Oracle Error 20202
Contents |
or May be I'm the only unlucky one, which has triggered me to write this blog. I'm sharing this information over this blog, In case some one upgrading to R12 make sure ora 20202 error that these settings/requirements are in place. Believe me, the solution is very simple but
Ora 20001 Oracle Error
to get to the root cause and finding a solution during upgrade down time is very very stressful. May be
Ora-06512
this information would be useful to some one. Wish, no one to get into such situation especially during PROD upgrade. Background: Upgrade Iteration 1: - We cloned 11.5.10.2 environment to a new server. - Completed functional steps to complete/enable multi org etc. - Copied over the DB to another machine, -Converted the DB to 64 bit and upgraded to 11.2.0.3 with Examples. -Installed R12.1.1 techstack. -Applied R12 upgrade patch, and then to R12.1.3 RUP. - OAS patching etc. - Some issues we encountered, but all went as planned. Upgrade Iteration 2: The same steps were followed, went ahead as planned. PROD Upgrade 3 : No cloning required, as we are doing this time on PROD. All the steps were executed successfully until R12.1.1 upgrade patch, the job ran for about 14 hours approximately and then some of the sql's were failing with the below error message. ERROR at line 1: ORA-20001: Please specify a valid printer. Either you have not specified a printer for your report, or the printer name you have given does not match that in the program definition. Please specify a printer in the program definition, report set definition, run reports form or as a profile option. ORA-06512: at "APPS.HR_UTILITY", line 939 ORA-06512: at line 46 and SQL> @bomcpbom.sql declare * ERROR at line 1: ORA-20202: Please specify a valid printer. Either you have not specified a printer for your report, or the printer name you have given does not match that in the program definition. Please specify a printer in the program definition, report set definition, run reports form or as a profile option. ORA-06512: at line 38 Initially, these were the steps taken. 1. Checked the worker log files --> Same error. 2. Tried executing the same sql from the sql> prompt --> Resulted in t
SQL TuningSecurityOracle UNIXOracle LinuxMonitoringRemote supportRemote plansRemote servicesApplication Server ApplicationsOracle FormsOracle PortalApp UpgradesSQL ServerOracle ConceptsSoftware SupportRemote Support Development Implementation Consulting StaffConsulting PricesHelp Wanted! Oracle PostersOracle Books Oracle Scripts Ion Excel-DB Don Burleson Blog
RMAN-20202 tips Expert Oracle Database Tips by Burleson Consulting March 8, 2015 Question: I am getting these errors when doing a tablespace point in time recovery (TSPITR) in RMAN: RMAN-03002: failure of recover command at 03/06/2011 15:07:27 RMAN-20202: Tablespace not found in the recovery catalog RMAN-06019: could not translate tablespace name "HRTEST" http://oraclelabspace.blogspot.com/2012/01/ora-20001ora-20202ora-06512-errors.html How do I fix the RMAN-20202 error? Answer:The oerr utility can display details on this error message: RMAN-20202: Tablespace not found in the recovery catalog Cause: the specified tablespace is not found in the recovery catalog Action: make sure that the tablespace name is correct and that the recovery catalog is up-to-date In your case, you need to confirm that this tablespace http://www.dba-oracle.com/t_rman_20202.htm name exists within your ORACLE_SID database by querying the dba_data_files view. select tablespace_name from dba_data_files where file_name = 'name of your HRTEST file'; Also, query the RMAN catalog database for details. Get the Complete Oracle Backup & Recovery Details The landmark book "Oracle Backup & Recovery: Expert secrets for using RMAN and Data Pump " provides real world advice for resolving the most difficult Oracle performance and recovery issues. Buy it for 40% off directly from the publisher. Burleson is the American Team Note: This Oracle documentation was created as a support and Oracle training reference for use by our DBA performance tuning consulting professionals. Feel free to ask questions on our Oracle forum. Verify experience! Anyone considering using the services of an Oracle support expert should independently investigate their credentials and experience, and not rely on advertisements and self-proclaimed expertise. All legitimate Oracle experts publish their Oracle qualifications. Errata? Oracle technology is changing and we strive to update our BC Oracle support information. If you find an error or have a suggestion for improving our content, we would appreciate your feedback.Thu, 17 Jan 2002 17:32:19 -0800 Message-ID:
RMAN-06019 Errors During RMAN TablespaceRestore August 23, 2012 talipozturk Leave a comment Go to comments These errors are occured when we try to restore a dropped tablespace. If we drop a tablespace then the controlfile will not keep any records related to the dropped tablespace. If we try to use the RMAN RESTORE or RECOVER TABLESPACE command, it will get the RMAN-20202, RMAN-06019 errors. Let's do a test # sqlplus / as sysdba SQL> create tablespace TS_TEST datafile ‘/data/test11g/ts_test.dbf' size 10M autoextend on; # rman target / RMAN> backup tablespace TS_TEST; Starting backup at 23-AUG-12 using target database control file instead of recovery catalog allocated channel: ORA_DISK_1 channel ORA_DISK_1: sid=144 devtype=DISK channel ORA_DISK_1: starting full datafile backupset channel ORA_DISK_1: specifying datafile(s) in backupset input datafile fno=00031 name=/data/test11g/ts_test.dbf channel ORA_DISK_1: starting piece 1 at 23-AUG-12 channel ORA_DISK_1: finished piece 1 at 23-AUG-12 piece handle=/oracle/yedek/bck_test11g/a8njcggd_1_1.bck tag=TAG20120823T153645 comment=NONE channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01 Finished backup at 23-AUG-12 Starting Control File Autobackup at 23-AUG-12 piece handle=/oracle/yedek/bck_test11g/cf_sp_file_c-1532875336-20120823-01 comment=NONE Finished Control File Autobackup at 23-AUG-12 # sqlplus / as sysdba SQL> drop tablespace TS_TEST including contents and datafiles; # rman target / RMAN> restore tablespace TS_TEST; Starting restore at 23-AUG-12 using target database control file instead of recovery catalog allocated channel: ORA_DISK_1 channel ORA_DISK_1: sid=136 devtype=DISK RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of restore command at 08/23/2012 15:38:40 RMAN-20202: tablespace not found in the recovery catalog RMAN-06019: could not translate tablespace name "TS_TEST" To recover a dropped tablespace, we must do a point in time recovery of the whole databa