Xempire Rebus/Riddle of the day

23/9

Riddle: Digitalkey =hash

Oracle : Experiment guaranteed restore point usage

At the start of this experiment Flashback is off. Meaning flashback is not a requirement for restore point.

V$database:Flashback_on=NO

 SQL> create restore point test guarantee flashback database;

Restore point created.


SQL> create table test (a number);

Table created.

SQL> insert into test values(1000);

1 row created.

SQL> commit;

Commit complete.

SQL> shut immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount
ORACLE instance started.

Total System Global Area 4496291200 bytes
Fixed Size                  9037184 bytes
Variable Size             872415232 bytes
Database Buffers         3607101440 bytes
Redo Buffers                7737344 bytes
Database mounted.

SQL> flashback database to restore point test;

Flashback complete.

SQL> shut immediate
ORA-01109: database not open


Database dismounted.
ORACLE instance shut down.
SQL> startup
ORACLE instance started.

Total System Global Area 4496291200 bytes
Fixed Size                  9037184 bytes
Variable Size             872415232 bytes
Database Buffers         3607101440 bytes
Redo Buffers                7737344 bytes
Database mounted.
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open


SQL> alter database open resetlogs;

Database altered.

SQL> drop restore point test;

Restore point dropped.

SQL> select * from test;
select * from test
              *
ERROR at line 1:
ORA-00942: table or view does not exist


SQL>

Linux: Experiment on incremental FS backup using tar

    Incremental backup using tar : good for file system backup/archiving of log directories etc. 

Commands: I am using LVL variable to ease my work in rewriting incremental backup. Start from 0 and go up from there.

export LVL=0

tar --verbose --create --file=tmp_${LVL}.tar --listed-incremental=tmp.snar tmp/*

Note: snar file remains same at all levels, it is the tracker for incremental changes.

Next just change LVL=1,2 ..... so on. Must or the tar file get overwritten.

If any of the files get changed or new file created, next level automatically picks it up.

Alternate Method(I prefer):See the variable --level (0 means base and the incrementals)

export LVL=1

tar --verbose --create --file=tmp_${LVL}.tar --listed-incremental=tmp.snar --level=${LVL} tmp/*

Note: Extracting tar is same as before, tar xvf in the order it was backed up.

Oracle : Auto index feature

Careful, I am endorsing any feature. Use judiciously. 

DOC: https://docs.oracle.com/en/database/oracle/oracle-database/19/admin/managing-indexes.html#GUID-FF3F7EF5-9468-48BC-8990-8189C1CBFD12

Auto Indexing feature

--create/make it available

EXEC DBMS_AUTO_INDEX.CONFIGURE('AUTO_INDEX_MODE','IMPLEMENT');

--create/keep invisible

EXEC DBMS_AUTO_INDEX.CONFIGURE('AUTO_INDEX_MODE','REPORT ONLY');

--Feature off

EXEC DBMS_AUTO_INDEX.CONFIGURE('AUTO_INDEX_MODE','OFF');

***AUTO_INDEX_SCHEMA configuration setting to specify schemas that can use auto indexes

-- exclusion list

EXEC DBMS_AUTO_INDEX.CONFIGURE('AUTO_INDEX_SCHEMA', 'MYSCHEMA', FALSE);

EXEC DBMS_AUTO_INDEX.CONFIGURE('AUTO_INDEX_SCHEMA', 'YOURSCHEMA', FALSE);

--remove from exclusion list i.e. include

EXEC DBMS_AUTO_INDEX.CONFIGURE('AUTO_INDEX_SCHEMA', 'HR', NULL);

--Clear exclude list

EXEC DBMS_AUTO_INDEX.CONFIGURE('AUTO_INDEX_SCHEMA', NULL, TRUE);

***Retition for unused indexes

AUTO_INDEX_RETENTION_FOR_AUTO

--retain for 30days

EXEC DBMS_AUTO_INDEX.CONFIGURE('AUTO_INDEX_RETENTION_FOR_AUTO', '30');

--default retention 373 days

EXEC DBMS_AUTO_INDEX.CONFIGURE('AUTO_INDEX_RETENTION_FOR_AUTO', NULL);

---Warning/Alert Applicable for Manually created indexes(Use judgement)

EXEC DBMS_AUTO_INDEX.CONFIGURE('AUTO_INDEX_RETENTION_FOR_MANUAL', '160');

EXEC DBMS_AUTO_INDEX.CONFIGURE('AUTO_INDEX_RETENTION_FOR_MANUAL', NULL);

**Auto index logs/tracking

EXEC DBMS_AUTO_INDEX.CONFIGURE('AUTO_INDEX_REPORT_RETENTION', '160');

EXEC DBMS_AUTO_INDEX.CONFIGURE('AUTO_INDEX_REPORT_RETENTION', NULL);        --default 373

**Specify tablespace for auto index

EXEC DBMS_AUTO_INDEX.CONFIGURE('AUTO_INDEX_DEFAULT_TABLESPACE', 'TBS_AUTO');

**Allocation for auto indexes

EXEC DBMS_AUTO_INDEX.CONFIGURE('AUTO_INDEX_SPACE_BUDGET', '15');   --15%

**Compression on off

EXEC DBMS_AUTO_INDEX.CONFIGURE('AUTO_INDEX_COMPRESSION','ON');

###**Reporting on auto index

REPORT_ACTIVITY and REPORT_LAST_ACTIVITY functions of the DBMS_AUTO_INDEX package

declare

  report clob := null;

begin

  report := DBMS_AUTO_INDEX.REPORT_ACTIVITY();

end;

declare

  report clob := null;

begin

  report := DBMS_AUTO_INDEX.REPORT_ACTIVITY(

              activity_start => TO_TIMESTAMP('2018-11-01', 'YYYY-MM-DD'),

              activity_end   => TO_TIMESTAMP('2018-12-01', 'YYYY-MM-DD'),

              type           => 'HTML',

              section        => 'SUMMARY',

              level          => 'BASIC');

end;

Lords Mobile : Challange heros ( Saint Seiya ) by ak :1 thru current challenge

Challenge 10

Dona , snow queen, boomister-Manual

Challenge 9

Challenge 8

Challenge 7

Automode

Chanllenge 6:

Manual mode: attack ahead of leader(and pillers at back to kill blue monster)

death night,sea squire,dark follower:auto mode

Challange 5:

Manual

Manual Mode

Challenge 4:

Challenge 3:

Automode

Another Combination:

Challenge 2:

Auto Mode

Challenge 1: 

Mode Manual: trick attack anyone near leader

Another Combination:

Mode Manual: trick attack anyone near leader

Oracle: Clone/Duplicate database from physical standby database

Basic steps:

1.Cancel MRP on Standby database/shutdown/startup(default opens in readonly mode).

2. Include target tns in source tnsnames.ora

3. Prepare target.

• Listener.ora
• source and target tns in tnsnames.ora
• passwd file from source in $ORACLE_HOME/dbs
• start instance in nomount. (New setup: need to cook init.ora either from source or any other way
• Verify paths like controlfile/datafile/logfile etc exist.

4. Fire the duplicate command.

-----------------------------------SYNTAX and MISC information------------------------------------------

 Procedure is same as copying from Primary database with minor difference, put physical standby on RO mode.

RO-Read only.

Steps:

1. Configure Listener(to listen for connection) & copy orapwd.

Sample:

LISTENER = 

  (ADDRESS_LIST =

        (ADDRESS=

          (PROTOCOL=IPC)

          (KEY= CloneDB.world)

        )

        (ADDRESS =

          (PROTOCOL = TCP)

         (Host =<CloneDB Host>)

          (Port = <PORT>)

        )

  )

SID_LIST_LISTENER =

  (SID_LIST =

    (SID_DESC =

      (SID_NAME = <CloneDB>)

      (ORACLE_HOME = <Valid Home Path>)

    )

  )

2. Prepare TNS: Both source(Physical Standby) and Destination and init.ora(copy from source and adjust for DB & LOG convert parameters)

Sample:(Format :'Source path','Target Path', ........for each path in source)

*.db_file_name_convert='/u02/ORACLE/dbs','/u001/oradata/db,'/u03/ORACLE/dbs','/u002/oradata/db'

*.log_file_name_convert='/u02/ORACLE/redo','/u003/oradata/db','/u03/ORACLE/redo','/u004/oradata/db'

3. Open Physical standby in RO mode:

a. Cancel recovery.: alter database recover managed standby database cancel;

b. Shutdown immediate.

c. startup (This will open physical standby in RO mode automatically) 

Note : TNS connection entries needed  in tnsnames.ora both side(source/target)

Fireup RMAN:

rman target sys/pwd@<physicalstandby tns>  auxiliary sys/pwd@<DuplicateDB tns>

run

{

allocate channel T1 type disk;

allocate channel T2 type disk;

allocate channel T3 type disk;

allocate channel T4 type disk;

allocate auxiliary channel A1 type disk;

allocate auxiliary channel A2 type disk;

allocate auxiliary channel A3 type disk;

allocate auxiliary channel A4 type disk;

DUPLICATE TARGET DATABASE TO 'sblut1db' FROM ACTIVE DATABASE NOFILENAMECHECK;

} 

Number of channels may help to speedup the duplication process, be aware of load on the system(IO/CPU).

Additional info:

a. if duplicate fails fix the problem, normally would be 'missed' path creation.

b. UNDO tablespace parameter should either same or commented altogether, if different duplication would fail.

 

Amazon Support CHAT & CALL

Amazon Support:
Got it from twitter @AmazonHelp :

https://t.co/qxoAolVWov?amp=1

https://www.amazon.in/gp/help/customer/contact-us/ref=in_sm_cu?nodeId=200507590/