App Engine - No Success, All Processing Suspended

App Engine - No Success, All Processing Suspended

E-AE: All Processing Suspended: Restart OPRID=PS, RUNID=RUN01, PI=6368
SOLUTION 200738047; E-AE: All Processing Suspended: Restart OPRID=PS, RUNID=RUN01, PI=833 (108,503)

Specific To:
Enterprise PeopleTools Any Release.

ISSUE:

Customer runs AE program via App Designer run button for Application Engine programs, in PT 8.4x. The program runs in DOS. and received this message in the log;


All Processing Suspended: Restart OPRID=PS, RUNID=RUN01, PI=833 (108,503)
Message Set Number: 108
Message Number: 503
Message Reason: All Processing Suspended: Restart OPRID=PS, RUNID=RUN01,PI=833 (108,503)

What is this about and what should be done?

This error can also occur when Application Engine programs are restartable and run via the Process Scheduler, and the last run was No Success - And an attempt re-run, rather than re-start will produce error as well.

RESOLUTION:

The cause of this message is that previously this same AE program was run using the same OPRID=PS & RUNID=RUN01. It was not Successful on initial run, and now an attempt to RUN the same program has occurred, instead of an attempt to RESTART the original that failed.

This message happened while the Customer was in Development phase of this AE program. It could have happened when this AE was in Production as well. However, what to do would have completely different emphasis depending on if this happens in Development or Productions.

During the development cycle, we would expect that this AE would have to run many times before it runs to Successful completion as we expect. So there could be a good number of times this would need to run, and most likely not all will be Successful. Have two choices here, 1) Use a different run control each time, ie, RUN02, RUN03, RUN04 etc. or 2) Remove the row from PS_AERUNCONTROL like this;

DELETE FROM PS_AERUNCONTROL WHERE PROCESS_INSTANCE=833

This will free up the RUN01 run control to be used again, with same OPRID & AE program.

If this program were in Prodcution - we would NOT want to just clear out the run control! With No Success AE programs, the recommended behavior is to look at logs and/or trace files, figure out what the problem was and fix the problem. Then do a Restart of the same Process Instance. This should be done via the Process Monitor, if the program ran through a Process Scheduler, and if the AE program was run outside the Process Scheduler, be sure the psae command parameters include the same OPRID RUNID & -I PROCESS_INSTANCE as was the original run - This will cause the program to start where it left off, and once the program goes to Success, the row is removed from PS_AERUNCONTROL automatically.

Peoplesoft - Sign on Process

Posted by Sandeep G on Friday, December 28, 2007 at 6:40 AM

Understanding Peoplesoft Sign on:

Basic step in Peoplesoft Sign on are:

1. Initial Connection: The application server starts, and uses the Connect ID and User ID specified in its configuration file (PSAPPSRV.CFG) to perform the initial connection to the database.

2. SELECT on security tables: After the Connect ID is verified, the application server performs a SELECT on various PeopleTools security tables, such as PSOPRDEFN, PSACCESSPRFL, and PSSTATUS. From these tables the application server gathers info such as User ID and password, symbolic ID, access ID, and access password. After the application server has the required information, it logs off from this initial connection.

3. Re-Connects with access ID: When the system verifies that the access ID is valid, the application server begins the persistent connection to the database that all PIA and windows three-tier clients use to access the database.

RMAN (Recovery Manager) Commands

CREATE CATALOG command

Create Oracle schema for the recovery catalog.

RMAN> CREATE CATALOG;

RMAN> CREATE CATALOG TABLESPACE rmants;

RMAN> CREATE VIRTUAL CATALOG; -- 11g R1

SQL> EXEC rman.DBMS_RCVCAT.CREATE_VIRTUAL_CATALOG; -- 11g R1

DROP CATALOG command

Remove Oracle schema from the recovery catalog.

RMAN> DROP CATALOG;

RESYNC CATALOG command

Perform a full resynchronization, which creates a snapshot control file and then copies any new or changed information from that snapshot control file to the recovery catalog.

RMAN> RESYNC CATALOG;

RMAN> RESYNC CATALOG FROM DB_UNIQUE_NAME prod_db;

RMAN> RESYNC CATALOG FROM DB_UNIQUE_NAME ALL;

UPGRADE CATALOG command

Upgrade the recovery catalog schema from an older version to the version required by the RMAN executable.

RMAN> UPGRADE CATALOG;

IMPORT CATALOG command

Import the metadata from one recovery catalog into another recovery catalog.

RMAN> IMPORT CATALOG cat@srcdb;

RMAN> IMPORT CATALOG rcat@inst DBID=2871507123;

RMAN> IMPORT CATALOG cat@srcdb DBID=1844750987, 61738563;

RMAN> IMPORT CATALOG cat@srcdb DB_NAME=prod2;

RMAN> IMPORT CATALOG cat@srcdb DB_NAME=prod3, prod4;

RMAN> IMPORT CATALOG rman/rman@catdb1 DB_NAME=prod1 NO UNREGISTER;

REGISTER command

Register the target database in the recovery catalog.

RMAN> REGISTER DATABASE;

RMAN> REGISTER CATALOG;

RMAN> REGISTER CATALOG TABLESPACE tbs-name;

UNREGISTER command

Unregister a database from the recovery catalog.

RMAN> UNREGISTER DATABASE;

RMAN> UNREGISTER DATABASE NOPROMPT;

RMAN> UNREGISTER DATABASE prod1;

RMAN> UNREGISTER DATABASE prod2 NOPROMPT;

RMAN> UNREGISTER DB_UNIQUE_NAME prod2;

RMAN> UNREGISTER DB_UNIQUE_NAME prod1 NOPROMPT;

RMAN> UNREGISTER DB_UNIQUE_NAME prod2 INCLUDING BACKUPS;

RMAN> UNREGISTER DB_UNIQUE_NAME prod3 INCLUDING BACKUPS NOPROMPT;

GRANT command

Grant privileges to a recovery catalog user.

RMAN> GRANT CATALOG FOR DATABASE prod1 TO vpc1; -- 11g R1

RMAN> GRANT REGISTER DATABASE TO bckop2;

RMAN> GRANT RECOVERY_CATALOG_OWNER TO rmanop1, rmanop3;

REVOKE command

Revoke privileges from a recovery catalog user.

RMAN> REVOKE CATALOG FOR DATABASE prod1 FROM vpc1; -- 11g R1

RMAN> REVOKE REGISTER DATABASE FROM bckop2;

RMAN> REVOKE RECOVERY_CATALOG_OWNER FROM bckop;

RESET DATABASE command

Inform RMAN that the SQL statement ALTER DATABASE OPEN RESETLOGS has been executed and that a new incarnation of the target database has been created, or reset the target database to a prior incarnation.

RMAN> RESET DATABASE TO INCARNATION 3;

STARTUP command

Startup the target database. This command is equivalent to the SQL*Plus STARTUP command.

RMAN> STARTUP;

RMAN> STARTUP PFILE=’/u01/app/oracle/admin/pfile/initsid.ora’

RMAN> STARTUP NOMOUNT;

RMAN> STARTUP MOUNT;

RMAN> STARTUP FORCE;

RMAN> STARTUP FORCE DBA;

RMAN> STARTUP FORCE DBA PFILE=c:\Oracle\Admin\pfile\init.ora;

RMAN> STARTUP FORCE NOMOUNT;

RMAN> STARTUP FORCE MOUNT DBA PFILE=/tmp/inittrgt.ora;

SHUTDOWN command

Shutdown the target database. This command is equivalent to the SQL*Plus SHUTDOWN command.

RMAN> SHUTDOWN;

RMAN> SHUTDOWN NORMAL;

RMAN> SHUTDOWN TRANSACTIONAL;

RMAN> SHUTDOWN IMMEDIATE;

RMAN> SHUTDOWN ABORT;

ALTER DATABASE command

Mount or open a database.

RMAN> ALTER DATABASE MOUNT;

RMAN> ALTER DATABASE OPEN;

RMAN> ALTER DATABASE OPEN RESETLOGS;

SHOW command

RMAN> SHOW ALL;

CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default

CONFIGURE BACKUP OPTIMIZATION OFF; # default

CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default

CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default

CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default

CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default

CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default

CONFIGURE ARCHIVELOG BACKUP COPIES FOR DISK TO 1; # default

CONFIGURE MAXSETSIZE TO UNLIMITED; # default

CONFIGURE DEVICE TYPE DISK PARALLELISM 1; # default

CONFIGURE DATAFILE BACKUP COPIES FOR SBT TO 1; # default

CONFIGURE ARCHIVELOG BACKUP COPIES FOR SBT TO 1; # default

CONFIGURE ENCRYPTION FOR DATABASE OFF; # default

CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default

CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE; # default -- Oracle 11g R2

CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default

CONFIGURE SNAPSHOT CONTROLFILE NAME TO '.../dbs/snapcf_sid.f'; # default

%F = dbid, day, month, year and sequence

%U = %u_%p_%c

%u = eight characters of the backup set and time ...

%p = piece number within the backupset

%c = copy number of the backup piece ...

RMAN> SHOW RETENTION POLICY;

RMAN> SHOW RETENTION POLICY FOR DB_UNIQUE_NAME ALL;

RMAN> SHOW DEVICE TYPE;

RMAN> SHOW DEVICE TYPE FOR DB_UNIQUE_NAME prod3;

RMAN> SHOW DEFAULT DEVICE TYPE;

RMAN> SHOW CHANNEL;

RMAN> SHOW MAXSETSIZE;

RMAN> SHOW BACKUP OPTIMIZATION;

RMAN> SHOW SNAPSHOT CONTROLFILE NAME;

RMAN> SHOW CONTROLFILE AUTOBACKUP;

RMAN> SHOW COMPRESSION ALGORITHM;

RMAN> SHOW ENCRYPTION ALGORITHM;

RMAN> SHOW ALL FOR DB_UNIQUE_NAME ALL;

RMAN> SHOW ALL FOR DB_UNIQUE_NAME 'STANDBY';

CONFIGURE command

RMAN> CONFIGURE CONTROLFILE AUTOBACKUP ON;

RMAN> CONFIGURE CONTROLFILE AUTOBACKUP OFF;

RMAN> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'cf%F';

RMAN> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '+BACKUP';

RMAN> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK CLEAR;

RMAN> CONFIGURE RETENTION POLICY TO REDUNDANCY 3;

RMAN> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;

RMAN> CONFIGURE RETENTION POLICY CLEAR;

RMAN> CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 2;

RMAN> CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 2;

RMAN> CONFIGURE ARCHIVELOG DELETION POLICY TO SHIPPED TO ALL STANDBY;

RMAN> CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY; --11g

RMAN> CONFIGURE ARCHIVELOG DELETION POLICY CLEAR;

RMAN> CONFIGURE DEFAULT DEVICE TYPE TO sbt;

RMAN> CONFIGURE DEFAULT DEVICE TYPE TO DISK;

RMAN> CONFIGURE DEVICE TYPE sbt PARALLELISM 3;

RMAN> CONFIGURE DEVICE TYPE DISK PARALLELISM 4;

RMAN> CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET;

RMAN> CONFIGURE CHANNEL DEVICE TYPE sbt;

RMAN> CONFIGURE CHANNEL DEVICE TYPE sbt PARMS='ENV=mml_env_settings';

RMAN> CONFIGURE CHANNEL DEVICE TYPE sbt PARMS 'ENV=(NSR_SERVER=bksrv1)';

RMAN> CONFIGURE CHANNEL DEVICE TYPE sbt PARMS 'BLKSIZE=1048576';

RMAN> CONFIGURE CHANNEL DEVICE TYPE sbt FORMAT 'bkup_%U';

RMAN> CONFIGURE CHANNEL DEVICE TYPE sbt CLEAR;

RMAN> CONFIGURE CHANNEL 2 DEVICE TYPE sbt CONNECT 'SYS/pwd@node2' PARMS 'ENV=(NSR_SERVER=bksrv2)';

RMAN> CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/tmp/%U';

RMAN> CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 'C:\backup\df%t_s%s_s%p';

RMAN> CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT CLEAR;

RMAN> CONFIGURE CHANNEL DEVICE TYPE DISK DEBUG 5;

RMAN> CONFIGURE CHANNEL 2 DEVICE TYPE DISK FORMAT '/backup/db_%s%d_%p';

RMAN> CONFIGURE BACKUP OPTIMIZATION ON;

RMAN> CONFIGURE BACKUP OPTIMIZATION OFF;

RMAN> CONFIGURE SNAPSHOT CONTROLFILE NAME TO ‘/backup/snapcf_%d.f‘;

RMAN> CONFIGURE SNAPSHOT CONTROLFILE NAME TO ‘+FRA/snap/snapcf_%d.f‘;

RMAN> CONFIGURE SNAPSHOT CONTROLFILE NAME TO ‘/ocfs/oradata/snapcf‘;

RMAN> CONFIGURE SNAPSHOT CONTROLFILE NAME TO ‘/dev/sda‘;

RMAN> CONFIGURE MAXSETSIZE TO 100M;

RMAN> CONFIGURE MAXSETSIZE TO UNLIMITED;

RMAN> CONFIGURE CHANNEL DEVICE TYPE sbt MAXPIECESIZE 1G;

RMAN> CONFIGURE EXCLUDE FOR TABLESPACE example;

RMAN> CONFIGURE EXCLUDE CLEAR;

RMAN> CONFIGURE AUXNAME FOR DATAFILE 4 TO '/oracle/auxfiles/aux_4.f';

RMAN> CONFIGURE AUXNAME FOR DATAFILE 2 CLEAR;

RMAN> CONFIGURE COMPRESSION ALGORITHM 'BZIP2';

RMAN> CONFIGURE COMPRESSION ALGORITHM 'ZLIB'; --11g R1

RMAN> CONFIGURE COMPRESSION ALGORITHM 'LOW'; --11g R2,corresponds to LZO

RMAN> CONFIGURE COMPRESSION ALGORITHM 'MEDIUM'; --11g R2,corresponds to ZLIB

RMAN> CONFIGURE COMPRESSION ALGORITHM 'HIGH'; --11g R2,corresponds to unmodified BZIP2

RMAN> CONFIGURE COMPRESSION ALGORITHM 'BASIC'; --11g R2,corresponds to BZIP2

RMAN> CONFIGURE DB_UNIQUE_NAME 'standby' CONNECT IDENTIFIER 'standby_cs';

RMAN> CONFIGURE DEFAULT DEVICE TYPE TO DISK FOR DB_UNIQUE_NAME 'standby';

RMAN> CONFIGURE DEFAULT DEVICE TYPE TO DISK FOR DB_UNIQUE_NAME ALL;

RMAN> CONFIGURE DEFAULT DEVICE TYPE TO SBT FOR DB_UNIQUE_NAME po;

DBID - A unique 32-bit identification number computed when the database is created. RMAN displays the DBID upon connection to the target database. We can obtain the DBID by querying V$DATABASE or RC_DATABASE.

NEWNAME FOR DATAFILE - The default name for all subsequent RESTORE or SWITCH commands that affect the specified datafile.

MAXCORRUPT FOR DATAFILE - A limit on the number of previously undetected physical block corruptions that Oracle will allow in the datafile(s).

AUTOLOCATE - Force RMAN to automatically discover which nodes of an Oracle Real Application Clusters configuration contain the backups that you want to restore.

RMAN> SET ECHO ON;

RMAN> SET ECHO OFF;

RMAN> SET DATABASE prod;

RMAN> SET DBID=4240978820;

RMAN> SET DBID 591329635;

RMAN> SET COMMAND ID TO 'rman';

RMAN> SET MAXCORRUPT FOR DATABASE TO 2;

RMAN> SET MAXCORRUPT FOR DATAFILE 1 TO 2;

RMAN> SET BACKUP COPIES = 2;

RMAN> SET NEWNAME FOR DATABASE TO '/oradata1/%b';

RMAN> SET NEWNAME FOR TABLESPACE users TO '/oradata2/%U';

RMAN> SET NEWNAME FOR DATAFILE 1 to ‘/oradata/system01.dbf’;

RMAN> SET NEWNAME FOR DATAFILE '/disk7/tbs11.f' TO '/disk9/tbs11.f';

RMAN> SET NEWNAME FOR TEMPFILE 1 TO '/newdisk/dbs/temp1.f';

RMAN> SET CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE sbt TO 'cf_%F';

RMAN> SET CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'cf_%F.bak';

RMAN> SET UNTIL TIME ’04-23-2010:23:50:04’;

RMAN> SET ARCHIVELOG DESTINATION TO '/oracle/temp_restore';

RMAN> SET COMPRESSION ALGORITHM 'LOW';

RMAN> SET COMPRESSION ALGORITHM 'LOW' OPTIMIZE FOR LOAD FALSE;

RMAN> SET COMPRESSION ALGORITHM 'MEDIUM';

RMAN> SET COMPRESSION ALGORITHM 'HIGH';

BACKUP command

Backs up Oracle database files, copies of database files, archived logs, or backup sets.

BACKUP FULL Options

RMAN> BACKUP DATABASE;

RMAN> BACKUP DATABASE TAG=’test backup’;

RMAN> BACKUP DATABASE COMMENT=’full backup’;

RMAN> BACKUP TAG 'weekly_full_db_bkup' DATABASE MAXSETSIZE 10M;

RMAN> BACKUP MAXSETSIZE 500M DATABASE PLUS ARCHIVELOG;

RMAN> BACKUP DURATION 00:60 DATABASE;

RMAN> BACKUP DURATION 00:30 MINIMIZE TIME DATABASE;

RMAN> BACKUP DURATION 00:45 MINIMIZE LOAD DATABASE;

RMAN> BACKUP DATABASE PLUS ARCHIVELOG;

RMAN> BACKUP DATABASE KEEP FOREVER;

RMAN> BACKUP DATABASE KEEP UNTIL TIME=’SYSDATE+30’;

RMAN> BACKUP DATABASE UNTIL 'SYSDATE+365' NOLOGS;

RMAN> BACKUP DATABASE NOEXCLUDE;

RMAN> BACKUP DATABASE NOEXCLUDE KEEP FOREVER TAG=’abc’;

RMAN> BACKUP DATABASE SKIP READONLY;

RMAN> BACKUP DATABASE SKIP OFFLINE;

RMAN> BACKUP DATABASE SKIP INACCESSIBLE;

RMAN> BACKUP DATABASE SKIP READONLY SKIP OFFLINE SKIP INACCESSIBLE;

RMAN> BACKUP DATABASE FORCE; -- backup read only database also

RMAN> BACKUP DATABASE NOT BACKED UP;

RMAN> BACKUP DATABASE NOT BACKED UP SINCE TIME=’SYSDATE–3’;

RMAN> BACKUP NOT BACKED UP SINCE TIME 'SYSDATE-10' MAXSETSIZE 500M DATABASE PLUS ARCHIVELOG;

RMAN> BACKUP DATABASE COPIES=2;

RMAN> BACKUP DATABASE FORMAT '/disk1/backups/db_%U.bck'

TAG quarterly KEEP UNTIL TIME 'SYSDATE+365' RESTORE POINT Q1FY10;

RMAN> BACKUP DEVICE TYPE DISK DATABASE;

RMAN> BACKUP DEVICE TYPE sbt DATABASE PLUS ARCHIVELOG;

RMAN> BACKUP DEVICE TYPE sbt DATAFILECOPY FROM TAG 'latest' FORMAT 'df%f_%d';

RMAN> BACKUP DEVICE TYPE sbt ARCHIVELOG LIKE '/disk%arc%' DELETE ALL INPUT;

RMAN> BACKUP DEVICE TYPE sbt BACKUPSET COMPLETED BEFORE 'SYSDATE-14'DELETE INPUT;

RMAN> BACKUP CHECK LOGICAL DATABASE;

RMAN> BACKUP VALIDATE CHECK LOGICAL DATABASE;

RMAN> BACKUP VALIDATE DATABASE;

RMAN> BACKUP VALIDATE DATABASE ARCHIVELOG ALL;

RMAN> BACKUP TABLESPACE test;

RMAN> BACKUP TABLESPACE system, users, tools;

RMAN> BACKUP TABLESPACE 4;

RMAN> BACKUP TABLESPACE gld PLUS ARCHIVELOG;

RMAN> BACKUP TABLESPACE invd INCLUDE CURRENT CONTROLFILE;

RMAN> BACKUP TABLESPACE appsd INCLUDE CURRENT CONTROLFILE PLUS ARCHIVELOG;

RMAN> BACKUP TABLESPACE dwh SECTION SIZE 100M;

RMAN> BACKUP SECTION SIZE 250M TABLESPACE datamart;

RMAN> BACKUP DATAFILE 1;

RMAN> BACKUP DATAFILE 3, 2, 14;

RMAN> BACKUP DATAFILE ‘/u01/data/...’;

RMAN> BACKUP DATAFILE 1 PLUS ARCHIVELOG;

RMAN> BACKUP KEEP FOREVER FORMAT '?/dbs/%U_longterm.cpy' TAG longterm_bck DATAFILE 1 DATAFILE 2;

RMAN> BACKUP SECTION SIZE 500M DATAFILE 6;

RMAN> BACKUP ARCHIVELOG ALL;

RMAN> BACKUP ARCHIVELOG ALL DELETE INPUT;

RMAN> BACKUP ARCHIVELOG LIKE '/arch%' DELETE ALL INPUT;

RMAN> BACKUP ARCHIVELOG FROM TIME ‘SYSDATE–3’;

RMAN> BACKUP ARCHIVELOG FROM SEQUENCE 100;

RMAN> BACKUP ARCHIVELOG FROM SEQUENCE 999 DELETE INPUT;

RMAN> BACKUP ARCHIVELOG NOT BACKED UP 2 TIMES;

RMAN> BACKUP ARCHIVELOG COMPLETION TIME BETWEEN 'SYSDATE-28' AND 'SYSDATE-7';

RMAN> BACKUP FORMAT='AL_%d/%t/%s/%p' ARCHIVELOG LIKE '%arc_dest%';

RMAN> BACKUP CURRENT CONTROLFILE;

OR

RMAN> SQL “ALTER DATABASE BACKUP CONTROLFILE TO ’’/u01/ .../bkctl.ctl’’ “;

RMAN> BACKUP CURRENT CONTROLFILE TO '/backup/cntrlfile.copy';

RMAN> BACKUP CONTROLFILE COPY ‘/u10/backup/control.bkp’;

RMAN> BACKUP SPFILE;

RMAN> BACKUP DEVICE TYPE sbt SPFILE ARCHIVELOG ALL;

RMAN> BACKUP DEVICE TYPE sbt DATAFILECOPY ALL NODUPLICATES;

RMAN> BACKUP RECOVERY FILES;

BACKUP set

RMAN> BACKUP BACKUPSET ALL;

RMAN> BACKUP BACKUPSET ALL FORMAT = ‘/u01/.../backup_%u.bak’;

RMAN> BACKUP BACKUPSET COMPLETED BEFORE ‘SYSDATE-3’ DELETE INPUT;

RMAN> BACKUP DEVICE TYPE sbt BACKUPSET COMPLETED BEFORE 'SYSDATE-14' DELETE INPUT;

RMAN> BACKUP COPIES 2 DEVICE TYPE sbt BACKUPSET ALL;

RMAN> BACKUP AS COMPRESSED BACKUPSET;

RMAN> BACKUP AS COMPRESSED BACKUPSET DEVICE TYPE DISK COPIES 2 DATABASE FORMAT '/disk1/db_%U', '/disk2/db_%U';

RMAN> BACKUP AS BACKUPSET DATAFILE '$ORACLE_HOME/oradata/users01.dbf','$ORACLE_HOME/oradata/tools01.dbf';

RMAN> BACKUP AS BACKUPSET DATAFILECOPY ALL;

RMAN> BACKUP AS BACKUPSET DATAFILECOPY ALL NODUPLICATES;

IMAGE copy

RMAN> BACKUP AS COPY DATABASE;

RMAN> BACKUP AS COPY COPY OF DATABASE FROM TAG 'test' CHECK LOGICAL TAG 'duptest';

RMAN> BACKUP AS COPY TABLESPACE 8;

RMAN> BACKUP AS COPY TABLESPACE test;

RMAN> BACKUP AS COPY TABLESPACE system, tools, users, undotbs;

RMAN> BACKUP AS COPY DATAFILE 1;

RMAN> BACKUP AS COPY DATAFILE 2 FORMAT '/disk2/df2.cpy' TAG my_tag;

RMAN> BACKUP AS COPY CURRENT CONTROLFILE;

RMAN> BACKUP AS COPY CURRENT CONTROLFILE FORMAT ‘/....’;

RMAN> BACKUP AS COPY ARCHIVELOG ALL;

RMAN> BACKUP AS COPY KEEP FOREVER NOLOGS CURRENT CONTROLFILE FORMAT '?/oradata/cf_longterm.cpy', DATAFILE 1 FORMAT '?/oradata/df1_longterm.cpy', DATAFILE 2 FORMAT '?/oradata/df2_longterm.cpy';

RMAN> BACKUP AS COPY DATAFILECOPY 'bar' FORMAT 'foobar';

RMAN> BACKUP AS COPY DATAFILECOPY '/disk2/df2.cpy' FORMAT '/disk1/df2.cpy';

Incremental backups

RMAN> BACKUP INCREMENTAL LEVEL=0 DATABASE;

RMAN> BACKUP INCREMENTAL LEVEL=1 DATABASE;

RMAN> BACKUP INCREMENTAL LEVEL=2 DATABASE;

RMAN> BACKUP INCREMENTAL LEVEL 2 CUMULATIVE DATABASE;

RMAN> BACKUP INCREMENTAL LEVEL 2 DATABASE;

RMAN> BACKUP INCREMENTAL LEVEL=0 DATABASE PLUS ARCHIVELOG;

RMAN> BACKUP INCREMENTAL LEVEL 1 CUMULATIVE SKIP INACCESSIBLE DATABASE;

RMAN> BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG 'incr' DATABASE;

RMAN> BACKUP DEVICE TYPE DISK INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG 'oltp' DATABASE;

RMAN> BACKUP DEVICE TYPE DISK INCREMENTAL FROM SCN 351986 DATABASE FORMAT '/tmp/incr_standby_%U';

RMAN> BACKUP INCREMENTAL FROM SCN 629184 DATAFILE 5 FORMAT '/tmp/ForStandby_%U' TAG 'FORSTANDBY';

RMAN> BACKUP INCREMENTAL LEVEL = --- tablespace/datafile

RMAN> LIST INCARNATION;

RMAN> LIST INCARNATION OF DATABASE;

RMAN> LIST INCARNATION OF DATABASE vis;

RMAN> LIST DB_UNIQUE_NAME ALL;

RMAN> LIST DB_UNIQUE_NAME OF DATABASE;

RMAN> LIST BACKUP;

RMAN> LIST BACKUP SUMMARY;

RMAN> LIST BACKUP BY FILE;

RMAN> LIST BACKUP OF DATABASE;

RMAN> LIST BACKUP OF DATABASE BY BACKUP;

RMAN> LIST BACKUP OF TABLESPACE test SUMMARY;

RMAN> LIST BACKUP OF DATAFILE 65;

RMAN> LIST BACKUP OF DATAFILE 11 SUMMARY;

RMAN> LIST BACKUP OF CONTROLFILE;

RMAN> LIST BACKUP OF ARCHIVELOG FROM SEQUENCE 2222;

RMAN> LIST BACKUP RECOVERABLE;

RMAN> LIST EXPIRED BACKUP;

RMAN> LIST EXPIRED BACKUP OF ARCHIVELOG ALL SUMMARY;

RMAN> LIST COPY;

RMAN> LIST COPY OF DATABASE ARCHIVELOG ALL;

RMAN> LIST COPY OF TABLESPACE appl_idx;

RMAN> LIST COPY OF DATAFILE 11, 60, 98;

RMAN> LIST COPY OF CONTROLFILE;

RMAN> LIST EXPIRED COPY;

RMAN> LIST BACKUPSET SUMMARY;

RMAN> LIST BACKUPSET 109;

RMAN> LIST BACKUPSET OF DATAFILE 1;

RMAN> LIST ARCHIVELOG;

RMAN> LIST CONTROLFILECOPY "/tmp/cntrlfile.copy";

RMAN> LIST SCRIPT NAMES;

RMAN> LIST ALL SCRIPT NAMES;

RMAN> LIST GLOBAL SCRIPT NAMES;

RMAN> LIST FAILURE; -- 11g R1

RMAN> LIST FAILURE 420 DETAIL; -- 11g R1

RMAN> LIST FAILURE ALL; -- 11g R1

REPORT command

Report backup status: database, files, and backups. Perform detailed analyses of the content of the recovery catalog.

RMAN> REPORT OBSOLETE;

RMAN> REPORT NEED BACKUP;

RMAN> REPORT NEED BACKUP DAYS=5;

RMAN> REPORT NEED BACKUP REDUNDANCY=3;

RMAN> REPORT NEED BACKUP RECOVERY WINDOW OF 7 DAYS;

RMAN> REPORT NEED BACKUP DATABASE;

RMAN> REPORT NEED BACKUP INCREMENTAL 1;

RMAN> REPORT UNRECOVERABLE;

RMAN> REPORT SCHEMA;

RMAN> REPORT SCHEMA AT TIME 'sysdate-20/1440';

CHANGE command

RMAN> CHANGE BACKUPSET 431 KEEP FOREVER NOLOGS;

RMAN> CHANGE BACKUPSET 100 UNAVAILABLE;

RMAN> CHANGE BACKUPSET 121,122,127,203,300 UNCATALOG;

RMAN> CHANGE BACKUP OF DATABASE TAG=’abc’ UNAVAILABLE;

RMAN> CHANGE BACKUP OF DATABASE DEVICE TYPE DISK UNAVAILABLE;

RMAN> CHANGE BACKUP OF SPFILE COMPLETED BEFORE 'SYSDATE-3' UNAVAILABLE;

RMAN> CHANGE BACKUP TAG 'consistent_db_bkup' KEEP FOREVER;

RMAN> CHANGE BACKUP TAG 'consistent_db_bkup' KEEP FOREVER NOLOGS;

RMAN> CHANGE BACKUP FOR DB_UNIQUE_NAME standby1 RESET DB_UNIQUE_NAME;

RMAN> CHANGE BACKUP FOR DB_UNIQUE_NAME st3 RESET DB_UNIQUE_NAME TO st2;

RMAN> CHANGE DB_UNIQUE_NAME FROM rdbms4 TO rdbms_dev;RMAN> CHANGE ARCHIVELOG ALL UNCATALOG;

RMAN> CHANGE CONTROLFILECOPY '/tmp/cf.cpy' UNCATALOG;

RMAN> CHANGE FAILURE 5 PRIORITY LOW;

CROSSCHECK command

Check whether files managed by RMAN, such as archived logs, datafile copies, and backup pieces, still exist on disk or tape.

RMAN> CROSSCHECK BACKUP;

RMAN> CROSSCHECK BACKUP TAG=’full db’;

RMAN> CROSSCHECK BACKUP COMPLETED BETWEEN ‘SYSDATE-7’ AND ‘SYSDATE–1’;

RMAN> CROSSCHECK BACKUP COMPLETED BETWEEN '01-JAN-10' AND '14-FEB-10';

RMAN> CROSSCHECK BACKUP DEVICE TYPE sbt COMPLETED BETWEEN '01-AUG-09' AND '31-DEC-09';

RMAN> CROSSCHECK BACKUP DEVICE TYPE DISK COMPLETED BETWEEN '01-JAN-10' AND '23-MAR-10';

RMAN> CROSSCHECK BACKUP OF DATABASE;

RMAN> CROSSCHECK BACKUP OF TABLESPACE warehouse;

RMAN> CROSSCHECK BACKUP OF TABLESPACE userd COMPLETED BEFORE 'SYSDATE-14';

RMAN> CROSSCHECK BACKUP OF TABLESPACES gld, invd;

RMAN> CROSSCHECK BACKUP OF DATAFILE 9;

RMAN> CROSSCHECK BACKUP OF DATAFILE 4 COMPLETED AFTER 'SYSDATE-14';

RMAN> CROSSCHECK BACKUP OF DATAFILE "?/oradata/dwh/system01.dbf" COMPLETED AFTER 'SYSDATE-14';

RMAN> CROSSCHECK BACKUP OF CONTROLFILE;

RMAN> CROSSCHECK BACKUP OF SPFILE;

RMAN> CROSSCHECK BACKUP OF ARCHIVELOG ALL;

RMAN> CROSSCHECK BACKUP OF ARCHIVELOG ALL SPFILE;

RMAN> CROSSCHECK COPY;

RMAN> CROSSCHECK COPY OF DATABASE;

RMAN> CROSSCHECK DATAFILECOPY 113, 114, 115;

RMAN> CROSSCHECK CONTROLFILECOPY '/tmp/control01.ctl';

RMAN> CROSSCHECK ARCHIVELOG ALL;

RMAN> CROSSCHECK BACKUPSET;

RMAN> CROSSCHECK BACKUPSET 1338, 1339, 1340;

RMAN> CROSSCHECK BACKUPPIECE TAG = 'nightly_backup';

RMAN> CROSSCHECK PROXY 789;

SQL command

Execute a SQL statement from within Recovery Manager.

SQL [CHANNEL ‘channel_id’] ‘command’;

RMAN> SQL 'ALTER TABLESPACE users ONLINE';

RMAN> SQL 'ALTER DATABASE DATAFILE 64 OFFLINE';

RMAN> SQL "ALTER SYSTEM ARCHIVE LOG CURRENT";

RMAN> SQL "ALTER SYSTEM SWITCH LOGFILE";

RMAN> SQL "ALTER DATABASE BACKUP CONTROLFILE TO TRACE";

RMAN> SQL "ALTER TABLESPACE users ADD DATAFILE ''/disk1/ora/users02.dbf'' SIZE 100K AUTOEXTEND ON NEXT 10K MAXSIZE 100K";

RESTORE command

Restore files from backup sets or from disk copies to the default or a new location.

RMAN> RESTORE DATABASE;

RMAN> RESTORE DATABASE VALIDATE;

RMAN> RESTORE DATABASE PREVIEW;

RMAN> RESTORE DATABASE PREVIEW SUMMARY;

RMAN> RESTORE DATABASE SKIP TABLESPACE temp, history;

RMAN> RESTORE DATABASE UNTIL SCN 154876;

RMAN> RESTORE TABLESPACE users;

RMAN> RESTORE TABLESPACE dwh1, dwh2;

RMAN> RESTORE TABLESPACE tbs1 PREVIEW;

RMAN> RESTORE TABLESPACE users VALIDATE;

RMAN> RESTORE DATAFILE 45;

RMAN> RESTORE DATAFILE 23 PREVIEW;

RMAN> RESTORE DATAFILE 12 VALIDATE;

RMAN> RESTORE CONTROLFILE;

RMAN> RESTORE CONTROLFILE FROM AUTOBACKUP;

RMAN> RESTORE CONTROLFILE FROM TAG 'monday_cf_backup';

RMAN> RESTORE CONTROLFILE VALIDATE;

RMAN> RESTORE CONTROLFILE TO '/tmp/autobkp.dbf' FROM AUTOBACKUP MAXSEQ 20 MAXDAYS 150;

RMAN> RESTORE SPFILE;

RMAN> RESTORE SPFILE FROM AUTOBACKUP;

RMAN> RESTORE ARCHIVELOG ALL VALIDATE;

RMAN> RESTORE ARCHIVELOG ALL PREVIEW;

RMAN> RESTORE ARCHIVELOG ALL PREVIEW RECALL;

RMAN> RESTORE ARCHIVELOG ALL DEVICE TYPE sbt PREVIEW;

RMAN> RESTORE STANDBY CONTROLFILE FROM TAG 'forstandby';

Restore the control file, (to all locations specified in the parameter file) then restore the database, using that control file:

STARTUP NOMOUNT;

RUN

{

ALLOCATE CHANNEL c1 DEVICE TYPE sbt;

RESTORE CONTROLFILE;

ALTER DATABASE MOUNT;

RESTORE DATABASE;

}

RECOVER command

Perform media recovery from RMAN backups and copies. Apply redo log files and incremental backups to datafiles or data blocks restored from backup or datafile copies, to update them to a specified time.

RMAN> RECOVER DATABASE;

RMAN> RECOVER DATABASE NOREDO;

RMAN> RECOVER DATABASE SKIP TABLESPACE temp;

RMAN> RECOVER DATABASE SKIP FOREVER TABLESPACE exam;

RMAN> RECOVER DATABASE UNTIL SCN 154876;

RMAN> RECOVER TABLESPACE users;

RMAN> RECOVER TABLESPACE dwh DELETE ARCHIVELOG MAXSIZE 2M;

RMAN> RECOVER DATAFILE 33;

RMAN> RECOVER DATAFILECOPY '/disk1/img.df' UNTIL TIME 'SYSDATE-7';

RMAN> RECOVER COPY OF DATABASE WITH TAG 'incr';

RMAN> RECOVER COPY OF DATABASE WITH TAG 'upd' UNTIL TIME 'SYSDATE - 7';

RMAN> RECOVER CORRUPTION LIST;

Restore and recover the whole database

RMAN> STARTUP FORCE MOUNT;

RMAN> RESTORE DATABASE;

RMAN> RECOVER DATABASE;

RMAN> ALTER DATABASE OPEN;

Restore and recover a tablespace

RMAN> SQL 'ALTER TABLESPACE users OFFLINE';

RMAN> RESTORE TABLESPACE users;

RMAN> RECOVER TABLESPACE users;

RMAN> SQL 'ALTER TABLESPACE users ONLINE';

Restore and recover a datafile

RMAN> SQL 'ALTER DATABASE DATAFILE 64 OFFLINE';

RMAN> RESTORE DATAFILE 64;

RMAN> RECOVER DATAFILE 64;

RMAN> SQL 'ALTER DATABASE DATAFILE 64 ONLINE';

Steps for media recovery:

1. Mount or open the Oracle database. Mount the database when performing whole database recovery, or open the database when performing online tablespace/datafile recovery.

2. To perform incomplete recovery, use the SET UNTIL command to specify the time, SCN, or log sequence number at which recovery terminates. Alternatively, specify the UNTIL clause on the RESTORE and RECOVER commands.

3. Restore the necessary files with the RESTORE command.

4. Recover the datafiles with the RECOVER command.

5. Place the database in its normal state. For example, open it or bring recovered tablespaces/datafiles online.

DELETE command

Delete backups and copies, remove references to them from the recovery catalog, and update their control file records to status DELETED.

RMAN> DELETE OBSOLETE;

RMAN> DELETE NOPROMPT OBSOLETE;

RMAN> DELETE NOPROMPT OBSOLETE RECOVERY WINDOW OF 7 DAYS;

RMAN> DELETE EXPIRED BACKUP;

RMAN> DELETE EXPIRED BACKUP DEVICE TYPE sbt;

RMAN> DELETE BACKUP OF DATABASE LIKE '/tmp%';

RMAN> DELETE NOPROMPT EXPIRED BACKUP OF TABLESPACE userd COMPLETED BEFORE 'SYSDATE-14';

RMAN> DELETE BACKUP OF SPFILE TABLESPACE users DEVICE TYPE SBT;

RMAN> DELETE ARCHIVELOG ALL;

RMAN> DELETE ARCHIVELOG ALL BACKED UP 2 TIMES TO DEVICE TYPE SBT;

RMAN> DELETE NOPROMPT ARCHIVELOG UNTIL SEQUENCE = 7300;

RMAN> DELETE EXPIRED ARCHIVELOG ALL;

RMAN> DELETE NOPROMPT EXPIRED ARCHIVELOG ALL;

RMAN> DELETE BACKUPSET 101, 102, 103;

RMAN> DELETE NOPROMPT BACKUPSET TAG weekly_bkup;

RMAN> DELETE FORCE NOPROMPT BACKUPSET TAG weekly_bkup;

RMAN> DELETE DATAFILECOPY "+DG_DATA/db/datafile/system.259.699468079";

RMAN> DELETE CONTROLFILECOPY '/tmp/cntrlfile.copy';

RMAN> DELETE BACKUP DEVICE TYPE SBT;

RMAN> DELETE BACKUP DEVICE TYPE DISK;

RMAN> DELETE COPY;

RMAN> DELETE EXPIRED COPY;

RMAN> DELETE COPY TAG 'lastest';

DROP DATABASE command

Delete the target database from disk and unregisters it.

RMAN> DROP DATABASE;

RMAN> DROP DATABASE NOPROMPT;

RMAN> DROP DATABASE INCLUDING BACKUPS;

RMAN> DROP DATABASE INCLUDING BACKUPS NOPROMPT;

DUPLICATE command

Use backups of the target database to create a duplicate database that we can use for testing purposes or to create a standby database.

RMAN> DUPLICATE TARGET DATABASE;

RMAN> DUPLICATE TARGET DATABASE TO dwhdb;

RMAN> DUPLICATE TARGET DATABASE TO test PFILE=/u01/apps/db/inittest.ora;

RMAN> DUPLICATE TARGET DATABASE TO devdb NOFILENAMECHECK;

RMAN> DUPLICATE DATABASE 'prod' DBID 139525561 TO 'dupdb' NOFILENAMECHECK;

RMAN> DUPLICATE TARGET DATABASE TO dup FROM ACTIVE DATABASE NOFILENAMECHECK PASSWORD FILE SPFILE;

RMAN> DUPLICATE TARGET DATABASE TO dupdb

LOGFILE GROUP 1 ('?/dbs/dupdb_log_1_1.f','?/dbs/dupdb_log_1_2.f') SIZE 200K, GROUP 2 ('?/dbs/dupdb_log_2_1.f','?/dbs/dupdb_log_2_2.f') SIZE 200K REUSE;

RMAN> DUPLICATE TARGET DATABASE TO dup FOR STANDBY FROM ACTIVE DATABASE PASSWORD FILE SPFILE PARAMETER_VALUE_CONVERT '/disk1', '/disk2'

SET DB_FILE_NAME_CONVERT '/disk1','/disk2'

SET LOG_FILE_NAME_CONVERT '/disk1','/disk2'

SET SGA_MAX_SIZE 200M SET SGA_TARGET 125M;

SWITCH command

Specify that a datafile copy is now the current datafile, i.e. the datafile pointed to by the control file. This command is equivalent to the SQL statement ALTER DATABASE RENAME FILE as it applies to datafiles.

RMAN> SWITCH DATABASE TO COPY;

RMAN> SWITCH TABLESPACE users TO COPY;

RMAN> SWITCH DATAFILE ALL;

RMAN> SWITCH DATAFILE '/disk1/tols.dbf' TO DATAFILECOPY '/disk2/tols.copy';

RMAN> SWITCH DATAFILE "+DG_OLD/db/datafile/sysaux.260.699468081" TO COPY;

RMAN> SWITCH TEMPFILE 1;

RMAN> SWITCH TEMPFILE 1 TO '/newdisk/dbs/temp1.f';

RMAN> SWITCH TEMPFILE ALL;

CATALOG command

Add information about file copies and user-managed backups to the catalog repository.

RMAN> CATALOG DATAFILECOPY '/disk1/old_datafiles/01_10_2009/users01.dbf';

RMAN> CATALOG DATAFILECOPY '/disk2/backup/users01.bkp' LEVEL 0;

RMAN> CATALOG CONTROLFILECOPY '/disk3/backup/cf_copy.bkp';

RMAN> CATALOG ARCHIVELOG '/disk1/arch1_731.dbf', '/disk1/arch1_732.dbf';

RMAN> CATALOG BACKUPPIECE '/disk1/c-874220581-20090428-01';

RMAN> CATALOG LIKE '/backup';

RMAN> CATALOG START WITH '/fs2/arch';

RMAN> CATALOG START WITH '/disk2/archlog' NOPROMPT;

RMAN> CATALOG START WITH '+dg2';

RMAN> CATALOG RECOVERY AREA;

ALLOCATE command

Establish a channel, which is a connection between RMAN and a database instance.

RMAN> ALLOCATE CHANNEL c1 DEVICE TYPE sbt;

RMAN> ALLOCATE CHANNEL ch DEVICE TYPE DISK FORMAT ‘C:\ORACLEBKP\DB_U%’;

RMAN> ALLOCATE CHANNEL t1 DEVICE TYPE DISK CONNECT 'sys/pwd@bkp1’;

RMAN> ALLOCATE CHANNEL c1 DEVICE TYPE sbt PARMS 'ENV=(OB_MEDIA_FAMILY=wholedb_mf)';

RMAN> ALLOCATE CHANNEL t1 DEVICE TYPE sbt PARMS 'ENV=(OB_DEVICE_1=tape1, OB_DEVICE_2=tape3)';

RMAN> ALLOCATE CHANNEL t1 TYPE 'sbt_tape' PARMS='SBT_LIBRARY=/usr/openv/netbackup/bin/libobk.so.1';

RMAN> ALLOCATE CHANNEL t1 TYPE 'sbt_tape' SEND "NB_ORA_CLIENT=CLIENT_MACHINE_NAME";

RMAN> ALLOCATE CHANNEL 'dev1' TYPE 'sbt_tape' PARMS 'ENV=OB2BARTYPE=ORACLE8, OB2APPNAME=ORCL, OB2BARLIST=MACHINENAME_ORCL_ARCHLOGS)';

RMAN> ALLOCATE AUXILIARY CHANNEL ac1 TYPE DISK;

RMAN> ALLOCATE AUXILIARY CHANNEL ac2 DEVICE TYPE sbt;

ALLOCATE CHANNEL FOR MAINTENANCE - allocate a channel in preparation for issuing maintenance commands such as DELETE.

RMAN> ALLOCATE CHANNEL FOR MAINTENANCE DEVICE TYPE DISK;

RMAN> ALLOCATE CHANNEL FOR MAINTENANCE DEVICE TYPE DISK FORMAT "/disk2/%U";

RMAN> ALLOCATE CHANNEL FOR MAINTENANCE DEVICE TYPE DISK CONNECT '@test1';

RMAN> ALLOCATE CHANNEL FOR MAINTENANCE DEVICE TYPE sbt;

RMAN> ALLOCATE CHANNEL FOR MAINTENANCE DEVICE TYPE sbt PARMS 'SBT_LIBRARY=/usr/local/oracle/backup/lib/libobk.so, ENV=(OB_DEVICE_1=tape2)';

RELEASE CHANNEL command

Release a channel that was allocated with an ALLOCATE CHANNEL or ALLOCATE CHANNEL FOR MAINTENANCE command.

RMAN> RELEASE CHANNEL;

RMAN> RELEASE CHANNEL c1;

BLOCKRECOVER command

Will recover the corrupted blocks.

RMAN> BLOCKRECOVER CORRUPTION LIST;

RMAN> BLOCKRECOVER DATAFILE 8 BLOCK 22;

RMAN> BLOCKRECOVER DATAFILE 7 BLOCK 233,235 DATAFILE 4 BLOCK 101;

RMAN> BLOCKRECOVER DATAFILE 2 BLOCK 12,13 DATAFILE 3 BLOCK 5,98,99 DATAFILE 4 BLOCK 19;

RMAN> BLOCKRECOVER DATAFILE 3 BLOCK 2,4,5 TABLESPACE sales DBA 4194405,4194412 FROM DATAFILECOPY;

RMAN> BLOCKRECOVER TABLESPACE dwh DBA 4194404,4194405 FROM TAG "weekly";

RMAN> BLOCKRECOVER TABLESPACE dwh DBA 94404 RESTORE UNTIL TIME 'SYSDATE-2';

ADVISE FAILURE command (From Oracle 11g R1)

Display repair options.

RMAN> ADVISE FAILURE;

RMAN> ADVISE FAILURE 555, 242;

RMAN> ADVISE FAILURE ALL;

RMAN> ADVISE FAILURE CRITICAL;

RMAN> ADVISE FAILURE HIGH;

RMAN> ADVISE FAILURE LOW;

RMAN> ADVISE FAILURE HIGH EXCLUDE FAILURE 625;

REPAIR FAILURE command (From Oracle 11g R1)

Repair one or more failures recorded in the automated diagnostic repository.

RMAN> REPAIR FAILURE;

RMAN> REPAIR FAILURE PREVIEW;

RMAN> REPAIR FAILURE NOPROMPT;

RMAN> REPAIR FAILURE USING ADVISE OPTION integer;

VALIDATE command

Examine a backup set and report whether its data is intact. RMAN scans all of the backup pieces in the specified backup sets and looks at the checksums to verify that the contents can be successfully restored.

RMAN> VALIDATE BACKUPSET 218;

RMAN> VALIDATE BACKUPSET 3871, 3890;

RMAN> VALIDATE DATABASE; -- 11g R1

RMAN> VALIDATE TABLESPACE dwh;

RMAN> VALIDATE DATAFILE 2;

RMAN> VALIDATE DATAFILE 4,8;

RMAN> VALIDATE DATAFILE 4 BLOCK 56;

RMAN> VALIDATE CURRENT CONTROLFILE;

RMAN> VALIDATE SPFILE;

RMAN> VALIDATE RECOVERY FILES;

RMAN> VALIDATE RECOVERY AREA;

RMAN> VALIDATE DB_RECOVERY_FILE_DEST;

SPOOL command

Write RMAN output to a log file.

RMAN> SPOOL LOG TO '/tmp/spool.log';

RMAN> SPOOL LOG TO '/tmp/backup.log' APPEND;

RMAN> SPOOL LOG OFF;

PRINT SCRIPT command

Display a stored script.

RMAN> PRINT SCRIPT backup_db;

RMAN> PRINT GLOBAL SCRIPT backup_db;

RMAN> PRINT GLOBAL SCRIPT gl_backup_db TO FILE "/tmp/gl_backupdb.rman";

REPLACE SCRIPT command

Replace an existing script stored in the recovery catalog. If the script does not exist, then REPLACE SCRIPT creates it.

RMAN> REPLACE SCRIPT backup_db {BACKUP DATABASE PLUS ARCHIVELOG;}

RMAN> REPLACE SCRIPT df {BACKUP DATAFILE &1 TAG &2.1 FORMAT '&3_%U';}

RMAN> REPLACE GLOBAL SCRIPT backup_db {BACKUP DATABASE PLUS ARCHIVELOG;}

RMAN> REPLACE GLOBAL SCRIPT gl_full_bkp FROM FILE '/tmp/script_file.txt';

EXECUTE SCRIPT command

Run an RMAN stored script.

RMAN> RUN {EXECUTE SCRIPT backup_whole;}

RMAN> RUN {EXECUTE SCRIPT backup_ts_any USING 'example';}

RMAN> RUN {EXECUTE SCRIPT backup_df USING 3 test_backup df3;}

RMAN> RUN {EXECUTE GLOBAL SCRIPT global_backup_db;}

DELETE SCRIPT command

Delete a stored script from the recovery catalog.

RMAN> DELETE SCRIPT backup_db;

RMAN> DELETE GLOBAL SCRIPT global_backup_db;

FLASHBACK DATABASE command

Return the database to its state at a previous time or SCN.

RMAN> FLASHBACK DATABASE TO SCN 411010;

RMAN> FLASHBACK DATABASE TO RESTORE POINT 'before_update';

TRANSPORT TABLESPACE command

Create transportable tablespace sets from backup for one or more tablespaces.

RMAN> TRANSPORT TABLESPACE example, tools

TABLESPACE DESTINATION '/disk1/trans' AUXILIARY DESTINATION '/disk1/aux' UNTIL TIME 'SYSDATE-15/1440';

RMAN> TRANSPORT TABLESPACE exam

TABLESPACE DESTINATION '/disk1/trans' AUXILIARY DESTINATION '/disk1/aux' DATAPUMP DIRECTORY dpdir DUMP FILE 'dmpfile.dmp' IMPORT SCRIPT 'impscript.sql' EXPORT LOG 'explog.log';

CONVERT command

Convert datafile formats for transporting tablespaces and databases across platforms.

RMAN> CONVERT DATABASE NEW DATABASE 'prodwin' TRANSPORT SCRIPT '/tmp/convertdb/transportscript' TO PLATFORM 'Microsoft Windows IA (32-bit)' DB_FILE_NAME_CONVERT '/disk1/oracle/dbs','/tmp/convertdb';

RMAN> CONVERT DATABASE ON DESTINATION PLATFORM CONVERT SCRIPT '/tmp/convertdb/convertscript.rman' TRANSPORT SCRIPT '/tmp/convertdb/transportscript.sql' NEW DATABASE 'prodwin' FORMAT '/tmp/convertdb/%U';

RMAN> CONVERT DATABASE ON DESTINATION PLATFORM CONVERT SCRIPT '/tmp/convert_newdb.rman' TRANSPORT SCRIPT '/tmp/transport_newdb.sql' NEW DATABASE 'prodaix' DB_FILE_NAME_CONVERT '/u01/oradata/datafile','+DATA';

RMAN> CONVERT TABLESPACE tbs_2 FORMAT '/tmp/tbs_2_%U.df';

RMAN> CONVERT TABLESPACE finance, hr TO PLATFORM 'Solaris[tm] OE (32-bit)' FORMAT '/tmp/transport_to_solaris/%U';

RMAN> CONVERT DATAFILE '/disk1/oracle/dbs/tbs_f1.df', '/disk1/oracle/dbs/ax1.f' FORMAT '+DATAFILE';

RMAN> CONVERT DATAFILE '/u01/oradata/datafile/system.dbf' FROM PLATFORM 'Linux x86 64-bit' FORMAT '+DATA/system.dbf';

RMAN> CONVERT DATAFILE

'/tmp/from_solaris/fin/fin01.dbf', '/tmp/from_solaris/fin/fin02.dbf',

'/tmp/from_solaris/hr/hr01.dbf', '/tmp/from_solaris/hr/hr02.dbf'

DB_FILE_NAME_CONVERT '/tmp/from_solaris/fin','/disk2/orahome/dbs/fin', '/tmp/from_solaris/hr','/disk2/orahome/dbs/hr'

FROM PLATFORM 'Solaris[tm] OE (64-bit)';

EXIT or QUIT Command

Exit the RMAN console.

RMAN> exit;

RMAN> quit;

SEND command

Send a vendor-specific quoted string to one or more specific channels.

RMAN> SEND 'OB_DEVICE tape1';

HOST command

Invoke an operating system command-line subshell from within RMAN or run a specific operating system command.

RMAN> HOST;

RMAN> HOST 'ls -lt /disk2/*';

RMAN> HOST '/bin/mv $ORACLE_HOME/dbs/*.arc /disk2/archlog/';

Table Statistics syntax

EXECUTE DBMS_STATS.GATHER_TABLE_STATS (ownname=> 'SYSADM', tabname=> 'Table Name', estimate_percent=>25,cascade=>TRUE);

How to disable Workflow Tiggers in Peoplesoft ?

How to disable Workflow Tiggers in Peoplesoft ?

Main Menu > PeopleTools > Workflow > Defaults & Messages > Set Workflow defaults
Uncheck Worklist Active and Email Active

Comparison between Peoplesoft and Fusion

Oracle Application Development Framework (Oracle ADF).

Oracle ADF is an end-to-end application development framework that allows you to develop enterprise solutions that search, display, create, modify, and validate data using web, wireless, desktop, or web services interfaces. Just like PeopleSoft applications are built on PeopleTools Framework, Fusion Applications are built on Oracle ADF. Oracle ADF builds on Java Platform, Enterprise Edition (Java EE) standards and open-source technologies to simplify and accelerate implementing service-oriented applications. Whereas PeopleTools is a black box type of development environment, Oracle ADF is more of a white box. This brings with it many new opportunities but also requires more investment from developers in learning the basic aspects of the underlying technology.

JDeveloper (jdeveloper.exe)

Just like Application Designer was the Integrated Development Environment (IDE) for building PeopleTools applications, JDeveloper is an IDE for building web applications. JDeveloper covers the full development lifecycle from design to deployment, with drag-and-drop data binding, visual UI design, and team development features built-in. JDeveloper can be used to build ADF Applications but is also an IDE for other technologies such as HTML, JSF, Java, and Swing.

Oracle Application Server

PeopleSoft Application Server (psadmin.exe) and Web Server (startpia) are the runtime environment required to deploy and run your PeopleTools applications. The runtime environment required to deploy and run your ADF web applications is Oracle Application Server or an alternative J2EE Web Application Server with ADF Runtime Installed. JDeveloper also comes with an embedded integrated server for testing and debugging your applications. Hence, you don’t need to deploy your application to the main application server to test it like you do with PeopleTools.

Meta Data XML Files

Unlike PeopleTools metadata which is stored in the database in various PeopleTools tables (psrecdefn, psfielddefn, pspaneldefn etc.), ADF metadata is captured and stored as XML. For instance, when you create a new page called CreateOrder, a CreateOrder.jspx file is created in your project. As you drag and drop components onto your page in the visual editor, XML tags for these components and their attributes are added to the XML file. In contrast to PeopleTools where the only way to alter PeopleTools metadata is through the Application Designer, a developer can directly edit the source of the XML file in addition to using the visual editor.
ADF Business Components

Business Components represent the logical data model for your application. The Entity Object and its attributes map to the database tables and columns, just like the record definition. Entity Objects have declarative validation and business logic. The View Object is used to create different views of the various entities, like the PeopleTools Record Definition of type View, but doesn’t require an actual view to be created in the database, which significantly reduces the number of views in the database. View Objects allow developers to create logical business objects like Person, Order etc. Attributes that don’t represent columns in the database, i.e. calculated fields, can easily be added to view objects. This removes the need for derived records. Business logic can be added to the Business Component objects at the various layers just like record and field PeopleCode.

Java

In PeopleTools, PeopleCode is the language that is used for business logic when declarative or definitional development isn’t possible. In ADF, the language used for business logic is Java. JSF Page, JSF Page Fragment This is the canvas for your User Interface. Developers drag and drop components such as tables, forms etc. onto their JSF page to create the user interface for users. They can drop HTML, JSF, or most likely, ADF Faces components onto their page.

ADF Faces Components

ADF Faces is a set of over 100 components for developers to use to create their pages. ADF Faces UI components include advanced tables with column sorting and row selection capability, tree components for displaying data hierarchically, color and date pickers, and a host of other PeopleTools to Fusion Quick Reference Guides Page 5 components such as menus, command buttons, shuttle choosers, and progress meters. ADF Faces components provide very interactive web 2.0 features such as drag and drop and partial page rendering. These ADF Faces components bind to the business object layer just as panelfields are bound to underlying recfields.

ADF Task Flow

The ADF Taskflow defines your transaction boundaries like your component definition. You define the pages that are a part of your transaction and the navigational flow between your pages and across your transaction.

Component Buffer

At runtime, the component buffer is the representation of your data structures and business logic for your transaction. It maintains the current row, state, and saving of the data to the database etc.

Application Module

The Application Module is the equivalent of the Component Buffer but is defined with your ADF Business Components. This allows for separation between your data/business logic and your user interface. You can test and run your application module in JDeveloper without having a User Interface.

Application Designer Build Project ADF Offline Database Designer

In PeopleSoft, you create record definitions and build your tables in Application Designer, based on the record definition. JDeveloper and ADF provide a number of sophisticated tools to design, diagram and maintain your database schema. This technology is called the ADF Offline Database Designer.

One user can see the rows in the job data while the other user cannot see in Job Data search page.

 (Applicable for most version of PeopleSoft HRMS 8 and for all version HRMS 8.3 and higher)

For these symptoms:

1. A user cannot view data that they have been granted access to on the Department Security Tree. 

2. A user can view data they have not been granted access to on the Department Security Tree.

3. User is receiving "No Matching Entries Found" when using a search record

4. The PS_SCRTY_TBL_DEPT becomes empty

Here are the troubleshooting steps :

1. Have you run the app engine process HR_FASTVIEW (via Setup HRMS > Security > Department Security > Update Dept Security)?

2. Is the Update Row Level Security checkbox enabled when running the HR_FASTVIEW process (via Setup HRMS > Security > Department Security > Update Dept Security)?

3. Is the As Of Date designated on HR_FASTVIEW the same date as your current Department Security Tree?

4. Are the effective dates of your departments less than or equal to the effective date of your current Department Security Tree?

5. Does the SETID and TREE_EFFDT of your Department Security Tree appear via the following SQL after running HR_FASTVIEW -> SELECT * FROM PS_R_PER505 and is TREE_EFFDT equal to the effective of your tree via Tree Manager?

6. Is your Department Security Tree named "DEPT_SECURITY"?

7. If you've added a new department via the Department Table, have you also added it to the DEPT_SECURITY tree?

8. Do your users have the appropriate Row Security permission list assigned to their user profile (via PeopleTools > Security > User Profiles > User Profiles > General Tab > Row Security field)?

9. Does the Row Security permission list assigned to your user contain the appropriate setids and associated departments (the setid/departments per each department security tree that the user should have access to), and do the departments have Read/Write access (via Setup HRMS > Security > Department Security > Setup Security Access)?

10. If updating Fast Security, are all three checkboxes enabled via the Update Dept Security run control page (Re-Fresh Type 1, 2 and 3)?

11. Are there any departments via Setup HRMS > Security > Department Security > Setup Security Access (PS_SCRTY_TBL_DEPT) that do not exist on your department security tree (these need to be in sync)?

12. For an employee that isn't retrieved via Job Data (for example), sql PS_JOB for the employee (SELECT EMPLID, SETID_DEPT FROM PS_JOB WHERE EMPLID = 'xxx'). Does the employee's setid value in SETID_DEPT on PS_JOB equal the SETID of the department security tree(s) entered on the user's row security permission list (HRMS > Security > Department Security > Setup Security Access)?