CTAS in Exadata (11.2.0.3) from 10gR2*10.2.0.4) = ORA-03120

I am doing a CTAS to migrate data from a table in 10gR2 (about 800 million rows) and after about 5 hours I get
ORA-03120:two-task conversion routine:integer overflow
CREATE TABLE X
TABLESPACE Z
NOLOGGING
AS
SELECT /*+ parallel (a,16) */
* from Y@dblink a
where a.partition_date <trunc(sysdate)
/

Hello;
Any chance you are using a JDBC driver?
Try changing it to : ( Workaround )
SQLNET.ALLOWED_LOGON_VERSION=8
OR = 9
This is an old bug if I remember correctly.
Bug 8730787
Best Regards
mseberg
Added to mine, but I'm unable to recreate the error. Using Oracle 11 client.
Found this
Action:     Administrator should set SQLNET_ALLOWED_LOGON_VERSION parameter
     on both client and servers to values that matches the minimum
     version supported in the system.
Edited by: mseberg on Feb 16, 2012 12:34 PM
Edited by: mseberg on Feb 16, 2012 12:36 PM

Similar Messages

Full import/export from 10gR2 to 11gR1 / ORA-39083: Object type PROCACT_SYS

Hi,
I did a full db export/import (data pump - skipped existing objects) from 10gR2 to 11gR1 (win2003 server). it looks like everything went fine except with this error:
is this a serious error? what should I do to fix this error?
ORA-39083: Object type PROCACT_SYSTEM failed to create with error:
ORA-20000: Incompatible version of Workspace Manager Installed
Failing sql is:
BEGIN
declare ver varchar2(100) ; dummy integer; compile_exception EXCEPTION; PRAGMA EXCEPTION_INIT(compile_exception, -06550); invalid_table EXCEPTION; PRAGMA EXCEPTION_INIT(invalid_table, -00942); procedure createErrorProc is begin execute immediate 'create or replace function system.wm$_check_install return boolean is begin return true ; end;' ; end ; begin
Processing object type DATABASE_EXPORT/SYSTEM_PROCOBJACT/PROCOBJ
ORA-39083: Object type PROCOBJ failed to create with error:
ORA-29357: object AUTO_TASK_CONSUMER_GROUP already exists
Failing sql is:
BEGIN
dbms_resource_manager.create_consumer_group('AUTO_TASK_CONSUMER_GROUP','System maintenance task consumer group','ROUND-ROBIN');COMMIT; END;
ORA-39083: Object type PROCOBJ failed to create with error:
ORA-06550: line 2, column 1:
PLS-00201: identifier 'BMS_SCHEDULER.DISABLE' must be declared
ORA-06550: line 2, column 1:
PL/SQL: Statement ignored
Failing sql is:
BEGIN
bms_scheduler.disable( 'SYS."WEEKNIGHT_WINDOW"',force=>TRUE);
dbms_scheduler.set_attribute_null( 'SYS."WEEKNIGHT_WINDOW"','SCHEDULE_NAME');
dbms_scheduler.set_attribute_null( 'SYS."WEEKNIGHT_WINDOW"','START_DATE');
dbms_scheduler.set_attribute_null( 'SYS."WEEKNIGHT_WINDOW"','END_
Processing object type DATABASE_EXPORT/SYSTEM_PROCOBJACT/POST_SYSTEM_ACTIONS/PROCACT_SYSTEM
Processing object type DATABASE_EXPORT/SCHEMA/PROCACT_SCHEMA
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/TABLE
ORA-39083: Object type TABLE failed to create with error:
ORA-00439: feature not enabled: Partitioning
Failing sql is:
CREATE TABLE "SYSTEM"."LOGSTDBY$APPLY_PROGRESS" ("XIDUSN" NUMBER, "XIDSLT" NUMBER, "XIDSQN" NUMBER, "COMMIT_SCN" NUMBER, "COMMIT_TIME" DATE, "SPARE1" NUMBER, "SPARE2" NUMBER, "SPARE3" VARCHAR2(2000)) PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 STORAGE( BUFFER_POOL DEFAULT) TABLESPACE "SYSAUX" PARTITION BY RANGE ("COMMIT_SCN") (PARTITION "P0" VALUES LESS THAN (0) PCTFREE 10 PCTUSED 4
ORA-39151: Table "SYSMAN"."AQ$_MGMT_NOTIFY_QTABLE_T" exists. All dependent metadata and data will be skipped due to table_exists_action of skip
ORA-39151: Table "SYSMAN"."AQ$_MGMT_NOTIFY_QTABLE_H" exists. All dependent metadata and data will be skipped due to table_exists_action of skip
Edited by: Odeh on Jul 29, 2009 12:49 PM
Edited by: Odeh on Jul 29, 2009 1:12 PM

Pl see if these MOS Docs help
730373.1 - ORA-39083 ORA-20000 Incompatible Version of Workspace Manager Installed
743097.1 - IMP-00017 ORA-20000 Importing older version of OWM into a higher version
HTH
Srini

Upgraded Db from 10gR2 to 11gR2 want to know how can we make use of mem_target & mem_max_size parameter

Hi Guys,
Wish u all a very happy new year.
We have upgraded our Client UAT system on solaris 10 from 10gR2(10.2.0.4) to 11.2.0.3 with latest PSU patch 11.2.0.3.8 Solaris SPark 64 bit.
Post DB upgrade new parameters have been incorporated into the system namely
1. Memory_Target
2. Memory_Max_Size.
Now although we have our SGA and PGA set to some specific values in our system, what i want to know is how can we utilize the Two parameters i named above in the system and
how can it provide me better performance in relationship with SGA and PGA set in the system.
Probably on what concept does Memory_Target and Memory_max_size parameters work in 11gR2 system.
It would be really great if some one can provide the details with explanation.
Your help is appreciated.
Regards,
Milan Rathod.

Hi,
Automatic Memory Management(AMM) was introduced in ORACLE 11g to automate the size of SGA and PGA(takes full control of managing memory)
To configure AMM ,need to initialize MEMORY_TARGET and MEMORY_MAX_TARGET parameters.
MEMORY_TARGET:
The amount of shared memory available for Oracle to use when dynamically controlling the SGA and PGA.
This parameter is dynamic, so the total amount of memory available to Oracle can be increased or decreased, provided it does not exceed the MEMORY_MAX_TARGET limit. The default value is "0".
MEMORY_MAX_TARGET:
This defines the maximum size the MEMORY_TARGET can be increased to without an instance restart.
If the MEMORY_MAX_TARGET is not specified, it defaults to MEMORY_TARGET setting.
Let say If you are setting MEMORY_MAX_TARGET=2GB, then oracle will use these 2GB to manage the memory(Boh SGA and PGA)
If you set db_cache_size=1GB based on your requirement , then AMM always retains this 1GB memory for db_cache_size and it will use the remainng 1GB memory for other processes.

11gR2 Infrastructure Upgrade Question(s) from 10gR2

Hello.
We are currently using both Linux (RHEL5) and Solaris (5.10) for all of our Oracle 10.2.0.5.0 RAC DBs. Weare NOT using ASM currently. So, we are going to upgrade our DBs to the latest version of 11gR2 - and this obviously will include our CRS. I know the ASM and CRS under 10g are now combined under the 11gR2 Grid Infracstructure. I have been revieiwing the Oracle Grid Infrastructre Installation Guides for both OSs. While these guides are centered on new installations, I do notice that each has a small appendix tied to upgrading activities (Appendix E in Solaris and Appendix F in Linux).
I also have a few papers I pulled from blogs related to these activities (e. g., a blog from David Marco and another from Martin Bach) where they are updating their clusterware from 10gR2 to 11gR2. So here are a a few questions I'd like to answer - one may be obvious from what I have already read.
1.) This may be the obvious or redundant question - almost the entire writeups in the earlier referenced appendices seem to center around an 11.x CRS to 11gR2. So are these appendices still the correct reference when going from 10gR2 to 11gR2? Just double checking myself/
2.) Sadly, we are not going to be utilizing ASM anytime soon (tied to $$ issues realted to fiber connections). We might later, however, go to ASM. Is there anything I should do in relation to this upgrade tied to ASM that might make it easier to say move over to ASM in the next year - or should I just ignore any references to ASM during this initial upgrade?
3.) Does anyone have any other additional document references/URLs that you might feel would be helpful in the overall 11gR2 upgrade process (both Infrastructure and/or DB)?
Thank you in advance for any help.
Matt

Hi Matt;
Please check below notes:
Minimizing Downtime During Production Upgrade [ID 478308.1]
Master Note For Oracle Database Upgrades and Migrations [ID 1152016.1]
Different Upgrade Methods For Upgrading Your Database [ID 419550.1]
How To Upgrade ASM from 10.2 to 11.1 (RAC)? [ID 736127.1]
I suggest Please also check my blog
http://heliosguneserol.wordpress.com/2010/06/17/move-to-oracle-database-11g-release-2-wiht-mike-dietrich/
In this pdf you can see patch of to upgrade db from x to n wiht many senerios wiht all related metalinks notes which is created by Oracle worker Mike Dietrich
Regard
Helios

Migrating from 10gR2 to 11gR2 using impdp with network_link fails

Hi,
I'm trying to migrate a database from 10gR2 (Novell SLES 10) to a new server (Novell SLES 11) with 11gR2. I created a database on the new system with all required users and tablespaces. Then I used impdp in 11g with a database link to the source database:
impdp system/pw@db NETWORK_LINK=X_SourceServer FULL=Y
This command fails immediately with ORA-39113: unable to determine database version. Even using the parameter VERSION=10.2.0 doesn't change the result.
The Oracle Upgrade Guide tells me that upgrading is possible from 10* to 11* and recommeds impdp and network link. Is the failure perhaps a bug in the NETWORK_LINK procedure? Should I better try expdp on the source and impdp on the target with a dumpfile as intermediate (the database ist rather big, so dealing with files across the network will take a lot of storage capacity)?
Has anyone tried this method with success?
Thanks
Friedhelm
Edited by: user8964905 on 02.09.2011 02:34

This is due to an bug. The workaround is in the DOC
IMPDP From 10g TO 11g Gives ORA-39113, ORA-4052 & ORA-6544 PL/SQL: internal error, arguments: [55916] (Doc ID 1062428.1)

Upgradation from 10gr2 RAC to 11gr2

I am trying to upgrade my RAC database from 10gr2 to 11gr2. But after successfully completing rootupgrade.sh on all nodes, I am not able to see the registered components. i.e. "crsctl stat res -t" is not working. Even the active version is also showing the older one. My 10gr2 setup is in raw device. Has anybody faced the same issue before? Please share.
Thanks in advance.

816916 wrote:
I am trying to upgrade my RAC database from 10gr2 to 11gr2. But after successfully completing rootupgrade.sh on all nodes, I am not able to see the registered components. i.e. "crsctl stat res -t" is not working. Even the active version is also showing the older one. My 10gr2 setup is in raw device. Has anybody faced the same issue before? Please share.
Thanks in advance.
Hi
please provide more details, what is your OS, what is the 10g version and what is the 11g version.
please post the output from crsctl status resource -t
Cheers

Going from 10gR2 to 11gR2 - any obvious performance 'pitfalls'?

Hi, there,
I'm moving some databases from 10gR2 to 11gR2. I was wondering whether there were any obvious pitfalls in performance that I should be aware of (like the optimizer ones in previous versions). I'm taking the SPFILE from 10gR2 and modifying it as little as possible to use as my 11gR2's SPFILE.
Also, I've heard murmurs of timezones being an issue in migrating to 11gR2? I'm either going to be using export/import or TTS to move my data. I wonder if the timezone issue is related to RMAN somehow.
Mark

Hi,
I performed an Upgrade from 10.2.0.4.4 to 11.2.0.1 two weeks ago.
I used a note from oracle support for manual upgrade to 11gR2
the database had database vault and also had auditing enabled.
these peculiarities are all covered in the note.
I would suggest that if you have auditing enabled, set the parameter audit_trail=none before you commence upgrade.
In addition make sure the you have tested the upgrade before implementing on your production environment, this would prepare you greatly.
after the upgrade, the timezone was upgraded to 11, database vault was turned on, EM upgraded, database vault application redeployed.
all the best
samuelk
Edited by: Samuel K on Feb 24, 2011 3:13 PM
Edited by: Samuel K on Feb 24, 2011 3:14 PM
Edited by: Samuel K on Feb 24, 2011 3:15 PM

How to view the file content from the directory? getting Error:ORA-21560

SQL> create directory READ_LOB_DIR as 'D:\Prj\Comm\Data';
CREATE OR REPLACE Procedure READ_FILE_LOB IS
-- Input Directory as specified in create directory
l_dir CONSTANT VARCHAR2(30) := 'READ_LOB_DIR';
-- Input File which is read word by word
l_fil CONSTANT VARCHAR2(30) := 'testfile.txt';
-- Separator Character between words is a BLANK (ascii = 32)
l_seb CONSTANT RAW(100) := UTL_RAW.CAST_TO_RAW(CHR(32));
-- Character at the end of the file is NEWLINE (ascii = 10)
l_sen CONSTANT RAW(100) := UTL_RAW.CAST_TO_RAW(CHR(10));
-- Pointer to the BFILE
l_loc BFILE;
-- Current position in the file (file begins at position 1)
l_pos NUMBER := 1;
-- Amount of characters have been read
l_sum BINARY_INTEGER := 0;
-- Read Buffer
l_buf VARCHAR2(500);
-- End of the current word which will be read
l_end NUMBER;
-- Return value
l_ret BOOLEAN := FALSE;
BEGIN
-- Mapping the physical file with the pointer to the BFILE
l_loc := BFILENAME(l_dir, l_fil);
-- Check if the file exists
l_ret := DBMS_LOB.FILEEXISTS(l_loc) = 1;
IF (l_ret) THEN
dbms_output.put_line('File ' || l_fil || ' in Directory ' || l_dir ||
' exists');
-- Open the file in READ_ONLY mode
DBMS_LOB.OPEN(l_loc, DBMS_LOB.LOB_READONLY);
LOOP
-- Calculate the end of the current word
l_end := DBMS_LOB.INSTR(l_loc, l_seb, l_pos, 1);
-- Process end-of-file
IF (l_end = 0) THEN
l_end := DBMS_LOB.INSTR(l_loc, l_sen, l_pos, 1);
l_sum := l_end - l_pos - 1;
DBMS_LOB.READ(l_loc, l_sum, l_pos, l_buf);
dbms_output.put_line(UTL_RAW.CAST_TO_VARCHAR2(l_buf));
EXIT;
END IF;
-- Read until end-of-file
l_sum := l_end - l_pos;
DBMS_LOB.READ(l_loc, l_sum, l_pos, l_buf);
dbms_output.put_line(UTL_RAW.CAST_TO_VARCHAR2(l_buf));
l_pos := l_pos + l_sum + 1;
END LOOP;
DBMS_LOB.CLOSE(l_loc);
ELSE
dbms_output.put_line('File ' || l_fil || ' in Directory ' || l_dir ||
' does not exist');
END IF;
EXCEPTION
WHEN OTHERS THEN
dbms_output.put_line('Error:' || SQLERRM);
DBMS_LOB.CLOSE(l_loc);
END;
The Text file content is...
Copyright 1996,2001 Oracle Corporation.     All Rights Reserved
This file contains installation instructions for installing the
Oracle8 ODBC Driver software.
It is divided into four parts:
o Part I: Summary of systems supported by Oracle8 ODBC client
software
Lists the platforms on which the Oracle8 ODBC Client software can
be installed.
o Part II: Oracle8 ODBC Driver software.
Describes the files, and installation prerequisites for the Oracle8
ODBC driver software.
o Part III: Exploding the kit onto your system
Describes how to explode the kit onto your system hard drive.
o Part IV: Installation Instructions
Describes how to install the Oracle8 ODBC driver.
Part I: Systems supported by the Oracle8 client software
You can install the ODBC client software on any of the following systems:
o Windows 2000
o Windows NT X86
o Windows 95
o Windows 98
The Oracle8 ODBC Driver provides support for ODBC connections
from Windows 2000, Windows NT, Windows 95, and Windows 98 systems
to Oracle databases.
o Part II: Oracle8 ODBC Driver software.
Refer to the following files for information about the Oracle8 ODBC Driver:
LICENSE.TXT - Oracle8 ODBC Driver License Agreement. Read carefully
before installing and/or using this product. Enclosed in
your software distribution kit.
SQORA.HLP - A Window's Help file which is the primary reference
          manual for the Oracle8 ODBC Driver.
ODBCRelnotes.WRI - The release notes for the Oracle8 ODBC Driver
which contains information which may have not been
included in the Help file.
Installation Prerequisites
See the Oracle8 ODBC Driver release notes (ODBCRelnotes.WRI),
for a complete list of software products required and their versions.
Time Required
The installation of the Oracle8 ODBC Driver takes approximately 5
minutes. The actual time may be shorter or longer, depending upon
your hardware configuration.
Disk Space Required
The Oracle8 ODBC driver installation requires approximately 2
megabytes of available storage space. The space required depends upon
what files you already have installed. The installation procedure
checks to see if you have enough available disk space. If you do not,
the installation fails.
Part III: Exploding the Kit onto your system
Expand the self-extracting archive file onto your hard drive.
C:\> ORA8174.EXE
Part IV: Installation Instructions
Oracle8 ODBC Driver 8.1.7.4.0
This section assumes the following:
1. MS Windows 2000, Windows NT, Windows 95 or Windows 98 is running.
2. Oracle Universal Installer shipping with 8.1.7 has already been
installed on your system.
3. Part III has been completed.
Software fixes:
Refer to release notes (ODBCRelnotes.wri) for a complete list of
Software fixes.
Installation Instructions
Once the self-extracting archive file ORA8174.EXE has been
exploded it will create an installable directory structure
onto your hard drive. Run the Oracle Universal Installer from
your local drive.
1. On the screen "File Locations" use the "Browse" button of
the source path to choose the file 'products.jar' from the
folder that ORA8174.EXE was extracted to. Choose 'Next'.
2. You will receive a warning that some of the dependencies of
this product are not found in the staging area. This warning
is OK. The ODBC driver depends on the Net8 Client being already
installed on the system. Answer 'Yes' to continue.
Oracle is a registered trademark of Oracle Corporation.
Microsoft, MS are registered trademarks of Microsoft Corporation.
Microsoft Windows, Windows NT, Windows 95, Windows 98 and Open Database
Connectivity are trademarks of Microsoft Corporation.
All other trademarks and registered trademarks are the property
of their respective owners.
The output was...
File testfile.txt in Directory READ_LOB_DIR exists
Copyright
1996,2001
Oracle
Corporation.
All
Rights
Reserved
This
file
contains
installation
instructions
for
installing
the
Oracle8
ODBC
Driver
software.
It
is
divided
into
four
parts:
o
Part
I:
Summary
of
systems
supported
by
Oracle8
ODBC
client
Error:ORA-21560: argument 2 is null, invalid, or out of range
I want to diplay/view as per file content format from the file under that specified directory.
Have any other method / any help or suggestions would be really appreciated.

I changed the code like...
CREATE OR REPLACE Procedure READ_FILE_LOB_tmp IS
-- Input Directory as specified in create directory
l_dir CONSTANT VARCHAR2(30) := 'READ_LOB_DIR';
-- Input File which is read word by word
l_fil CONSTANT VARCHAR2(30) := 'testfile.txt';
-- Separator Character between words is a BLANK (ascii = 32)
l_seb CONSTANT RAW(100) := UTL_RAW.CAST_TO_RAW(CHR(32));
-- Character at the end of the file is NEWLINE (ascii = 10)
l_sen CONSTANT RAW(100) := UTL_RAW.CAST_TO_RAW(CHR(10));
-- Pointer to the BFILE
l_loc BFILE;
-- Current position in the file (file begins at position 1)
l_pos NUMBER := 1;
-- Amount of characters have been read
l_sum BINARY_INTEGER := 0;
-- Read Buffer
l_buf VARCHAR2(4000);
-- End of the current word which will be read
l_end NUMBER;
-- Return value
l_ret BOOLEAN := FALSE;
BEGIN
-- Mapping the physical file with the pointer to the BFILE
l_loc := BFILENAME(l_dir, l_fil);
-- Check if the file exists
l_ret := DBMS_LOB.FILEEXISTS(l_loc) = 1;
IF (l_ret) THEN
dbms_output.put_line('File ' || l_fil || ' in Directory ' || l_dir ||
' exists');
-- Open the file in READ_ONLY mode
DBMS_LOB.OPEN(l_loc, DBMS_LOB.LOB_READONLY);
LOOP
-- Calculate the end of the current word
l_end := DBMS_LOB.INSTR(l_loc, l_sen, l_pos, 1);
-- Process end-of-file
IF (l_end = 0) THEN
EXIT;
END IF;
-- Read until end-of-file
l_sum := l_end - l_pos;
DBMS_LOB.READ(l_loc, l_sum, l_pos, l_buf);
dbms_output.put_line(UTL_RAW.CAST_TO_VARCHAR2(l_buf));
l_pos := l_pos + l_sum + 1;
END LOOP;
DBMS_LOB.CLOSE(l_loc);
ELSE
dbms_output.put_line('File ' || l_fil || ' in Directory ' || l_dir ||
' does not exist');
END IF;
EXCEPTION
WHEN OTHERS THEN
dbms_output.put_line('Error:' || SQLERRM);
DBMS_LOB.CLOSE(l_loc);
END;
Now its working fine with one addtional line...
The file content is...
This is My Content
This is My Content
This is My Content
This is My Content
This is My Content
But The output was...
File testfile.txt in Directory READ_LOB_DIR exists
This is My Content
This is My Content
This is My Content
This is My Content
This is My Content
here, i want to delete that additonal line...?

RMAN-06004:ORACLE error from recovery catalog ... ORA-00904: : invalid ...

Good Morning All,
One of our RMAN backups is failing with the following error message. Any suggestions would be greatly appreciated.
==================================================================================================
Starting backup at 12/30/2008 22:03:47
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 12/30/2008 22:03:47
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> ##BACKUP ARCHIVELOG ALL FORMAT '%d_bkp_al_%t_Set%s_Piece%p' delete input;
2>
3> # DELETE ARCHIVELOG UNTIL TIME 'SYSDATE-7';
4>
5> # check if database can be restored
6> # RESTORE DATABASE VALIDATE;
7>
8> # check if controlfile can be restored
9> ##RESTORE CONTROLFILE to '/backups/admin/custpr/custpr_bkp_cntlfile.ctl' VALIDATE;
10>
11> # check if archivelogs for the past two weeks can be restored
12> # RESTORE ARCHIVELOG FROM TIME 'SYSDATE-7' VALIDATE;
13>
14> # - Verify all backups on backup media are intact
15> # CROSSCHECK BACKUP OF DATABASE;
16>
17> # - Display a list of files that need to be backed up based on the retention
18> # policy. For this case study, files that don't have at least 1 backups
19> # will be reported.
20> REPORT NEED BACKUP;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 7 days
Report of files whose recovery needs more than 7 days of archived logs
File Days Name
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of report command at 12/30/2008 22:03:48
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> # - delete un-necessary backups. This command deletes backups based on the
2> # retention policy.
3> ######### commented out DELETE OBSOLETE - TSM not configured to delete on 68
4> #########DELETE OBSOLETE;
5>
6> # - get complete list of existing backups
7> LIST BACKUP;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of list command at 12/30/2008 22:03:49
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> #-end of file-
2> **end-of-file**
RMAN>
Edited by: ORA_UMAIR on Dec 31, 2008 7:51 AM

This Oracle Database is 9.2.0.6.0. Here is the complete log file. The RMAN script that I am using ran successfully many times before.
====================================================================================================
Recovery Manager: Release 9.2.0.6.0 - 64bit Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
RMAN>
connected to recovery catalog database
RMAN>
connected to target database: CUSTPR (DBID=525071053)
RMAN>
RMAN> #########################################################################
2> # LEVEL 0 BACKUP #
3> #########################################################################
4>
5> # Configure backups to be written to disk.
6> CONFIGURE DEFAULT DEVICE TYPE TO DISK;
old RMAN configuration parameters:
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
new RMAN configuration parameters:
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Set the retention policy to a recovery window of 7 days. This ensures that
2> # RMAN retains all backups needed to recover the database to any point in time
3> # in the last 7 days. You can use the DELETE OBSOLETE command to delete
4> # backups that are no longer required by the retention policy. To exclude a
5> # backup from consideration by the policy, you can use KEEP option with the
6> # BACKUP command.
7> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
old RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
new RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Configure RMAN to use two disk channels for backup, restore, recovery, and
2> # maintenance operations.
3> CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
old RMAN configuration parameters:
CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
new RMAN configuration parameters:
CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Configure RMAN to write disk backups to the /backup directory.
2> # The format specifier %t is replaced with a 4-byte timestamp, %s with the
3> # backup set number, and %p with the backup piece number.
4> CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
old RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
new RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Configure RMAN to back up the control file after each backup.
2> CONFIGURE CONTROLFILE AUTOBACKUP ON;
old RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
new RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Configure RMAN to write controlfile autobackups to the /backup directory.
2> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
old RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
new RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Enable the backup optimization feature introduced in 9i to make sure that
2> # RMAN won't backup an archivelog or datafile if there already exists a backup
3> # of that file. The FORCE option can be used to override optimization on a
4> # specific BACKUP command.
5> CONFIGURE BACKUP OPTIMIZATION ON;
old RMAN configuration parameters:
CONFIGURE BACKUP OPTIMIZATION ON;
new RMAN configuration parameters:
CONFIGURE BACKUP OPTIMIZATION ON;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Use the SHOW ALL command to see the current configuration settings.
2> SHOW ALL ;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%d_bkp_cf%F';
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 1;
CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' FORMAT '%d_bkp_df%t_Set%s_Piece%p';
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/orahome2/custprdb/9.2.0/dbs/snapcf_custpr.f'; # default
RMAN>
RMAN> # The following commands are run each day to start the backup cycle.
2> # The steps are:
3> # - Take an incremental level 0 backup of the database. A level 0 backup is
4> # a complete backup of the entire file which can be used as the basis
5> # for a subsequent incremental backup.
6> # - Backup all archivelogs that have not already been backed up.
7> # - Delete on-disk archivelogs older than seven days.
8>
9> BACKUP INCREMENTAL LEVEL 0 FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p'
10> DATABASE maxsetsize 33G
11> PLUS ARCHIVELOG FORMAT '/backups/admin/custpr/%d_bkp_al%t_Set%s_Piece%p'
12> delete all input;
Starting backup at 12/30/2008 22:01:40
current log archived
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=11 devtype=DISK
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=8008 recid=7910 stamp=674638862
input archive log thread=1 sequence=8009 recid=7911 stamp=674671207
input archive log thread=1 sequence=8010 recid=7912 stamp=674697380
input archive log thread=1 sequence=8011 recid=7913 stamp=674780433
input archive log thread=1 sequence=8012 recid=7914 stamp=674784211
input archive log thread=1 sequence=8013 recid=7915 stamp=674863288
input archive log thread=1 sequence=8014 recid=7916 stamp=674863300
channel ORA_DISK_1: starting piece 1 at 12/30/2008 22:01:41
channel ORA_DISK_1: finished piece 1 at 12/30/2008 22:03:47
piece handle=/backups/admin/custpr/CUSTPR_bkp_al674863300_Set3083_Piece1 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:02:07
channel ORA_DISK_1: deleting archive log(s)
archive log filename=/custpr/arch/arch_custpr_8008.log recid=7910 stamp=674638862
archive log filename=/custpr/arch/arch_custpr_8009.log recid=7911 stamp=674671207
archive log filename=/custpr/arch/arch_custpr_8010.log recid=7912 stamp=674697380
archive log filename=/custpr/arch/arch_custpr_8011.log recid=7913 stamp=674780433
archive log filename=/custpr/arch/arch_custpr_8012.log recid=7914 stamp=674784211
archive log filename=/custpr/arch/arch_custpr_8013.log recid=7915 stamp=674863288
archive log filename=/custpr/arch/arch_custpr_8014.log recid=7916 stamp=674863300
Finished backup at 12/30/2008 22:03:47
Starting backup at 12/30/2008 22:03:47
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 12/30/2008 22:03:47
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> ##BACKUP ARCHIVELOG ALL FORMAT '%d_bkp_al_%t_Set%s_Piece%p' delete input;
2>
3> # DELETE ARCHIVELOG UNTIL TIME 'SYSDATE-7';
4>
5> # check if database can be restored
6> # RESTORE DATABASE VALIDATE;
7>
8> # check if controlfile can be restored
9> ##RESTORE CONTROLFILE to '/backups/admin/custpr/custpr_bkp_cntlfile.ctl' VALIDATE;
10>
11> # check if archivelogs for the past two weeks can be restored
12> # RESTORE ARCHIVELOG FROM TIME 'SYSDATE-7' VALIDATE;
13>
14> # - Verify all backups on backup media are intact
15> # CROSSCHECK BACKUP OF DATABASE;
16>
17> # - Display a list of files that need to be backed up based on the retention
18> # policy. For this case study, files that don't have at least 1 backups
19> # will be reported.
20> REPORT NEED BACKUP;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 7 days
Report of files whose recovery needs more than 7 days of archived logs
File Days Name
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of report command at 12/30/2008 22:03:48
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> # - delete un-necessary backups. This command deletes backups based on the
2> # retention policy.
3> ######### commented out DELETE OBSOLETE - TSM not configured to delete on 68
4> #########DELETE OBSOLETE;
5>
6> # - get complete list of existing backups
7> LIST BACKUP;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of list command at 12/30/2008 22:03:49
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> #-end of file-
2> **end-of-file**
RMAN>
Recovery Manager complete.

From pl/sql table getting error - "ORA-01403: no data found"

Hi All,
i habe written package, and the spce define as -
type F761RecType is RECORD (
type F761TabType is TABLE of F761RecType INDEX BY BINARY_INTEGER;
l_F761_table F761TabType;
PROCEDURE modification1
p_F761_table IN F761TabType,
From button click of form i passed -
DECLARE
l_f761_table I743_PUC_MAPS_TREE_PKG.F761TabType;
l_counter number;
BEGIN
          LOOP
     l_counter :=l_counter+1;
          l_f761_table(l_counter).P_TABLE := :MAPS.P_table;
     EXIT WHEN      :SYSTEM.LAST_RECORD = 'TRUE' ;
next_record;
end loop;
i743_puc_maps_tree_pkg.modification1(
                                        p_F761_table => l_f761_table,
END;
Now when I take table count (l_f761_table.count) in button click in form level I am getting value; but when I try to get the count in sid the package, it giving error "ORA-01403: no data found".
Pls tell me where I am wrong ..!!
BR,
Subir

Thaks all, probls has been solved..

Tables do not import when importing from 10gR2 to 9iR2

Hello forum members
I take full database dump from 10g database as below:
C:\Documents and Settings\Vugar>exp
Export: Release 9.2.0.1.0 - Production on Thu Aug 6 19:05:47 2009
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Username: sys/sys_pass@prod as sysdba
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Produc
tion
With the Partitioning, OLAP and Data Mining options
Enter array fetch buffer size: 4096 >
Export file: EXPDAT.DMP > c:\full6.dmp
(1)E(ntire database), (2)U(sers), or (3)T(ables): (2)U > E
Export grants (yes/no): yes >
Export table data (yes/no): yes >
Compress extents (yes/no): yes >
And import the dump file in 9i database as below:
C:\Documents and Settings\Vugar>imp
Import: Release 9.2.0.1.0 - Production on Thu Aug 6 19:08:18 2009
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Username: sys/sys_pass as sysdba
Connected to: Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.1.0 - Production
Import file: EXPDAT.DMP > c:\full6.dmp
Enter insert buffer size (minimum is 8192) 30720>
Export file created by EXPORT:V09.02.00 via conventional path
import done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character set
import server uses AL32UTF8 character set (possible charset conversion)
List contents of import file only (yes/no): no >
Ignore create error due to object existence (yes/no): no >
Import grants (yes/no): yes >
Import table data (yes/no): yes >
Import entire export file (yes/no): no > Y
Everything goes alright, all of the users and their grants created in the target database. But the tables and other objects of users do not create. After the full import I import every user with the from user to user clause. After that all of the objects create under each user. Can anyone tell me the reason of that, why the objects of users do not create when perfomin full import?? What is my mistake in full importing?
Thanks.

Shafi Rasulov wrote:
Thanks for reply
Virendra, I exported from 10g with 9i exp utility, so 9i exp utility doesn't export incompatible objects from 10g, so it is possible full export import from 10g to 9i.
Anand, as you say, I exported/imported with 9i utility from 10g. In tha documentation and another tutorials I haven't seen any notification about missing table and another objects in the export/import.
Pavan, as you say there is several ways for migrating from 10g to 9i but I'm interested in why full export/import doesn't create tables and another objects when I do.
I say again, after I full import, I import each user with the FROM USER TO USER statement and all of the objects are created under relevant user. I want to learn the reason why the tables and another objects are not created in full import??I don't have 9i database with me to check what is happening but there should not be any error if you have used proper binary of the right version to do the export. What are those "incompatible objects" that you are talking about which are not exported/imported? You don't need to use from user/to user, if you are going to mention a 10g schema and Full=y , your import would work properly.
HTH
Aman....

Migrating from 10gR2 DB Control to Grid Control

hi
i've installed an Oracle10gR2 database with Database Control. now, i'd like to use Grid Control for managing both the 10g as well as an Oracle9iR2 database running on the same server. i'd like to use the existing Oracle10gR2 database as a management repository for Grid Control.
how should i install Grid Control on the server? do i just install Grid Control without worrying about the Database Control installation or do i need to do some sort of a migration for the management service or management repository or any other DB Control components? i don't currently have any valuable info in the repository so i can recreate it if it makes things easier.
are there any recommendations on where to place the GC installation on the file system? should it live in the database installation tree or in a separate tree?
br. aspa

I successfully installed the repository into a 10gR2 database today. The problem is the Repsitory schema user script fails when it attempts to create SYSMAN because 10gR2 databases have a problem with QUOTA UNLIMITED portion of the create user command issued by the OUI or underlying script called. You can comment out the QUOTA UNLIMITED sections and it will install and work fine from what I have seen.
You can find the script in the Oracle Management Services Home @ $ORACLE_HOME\sysman\admin\emdrep\sql\core\latest\admin\admin_create_repos_user.sql

Moving from 10gR2 Db on Unix (Tru64) to a new Linux server (10gR2)

Hi,
We are planning on moving our oracle 10gR2 Db on Unix (Tru64) to a new Linux server (same database 10gR2). Interested in discussing the easiest way for a newbie to get the data over to the new box. We currently perform a 'COLD" backup and have no transaction logging. The database is a data warehouse so stopping the database and backing up the files is not a issue. The database size is 500GB.
The Oracle ADDM on our current box is showing "individual database segments responsible for significant user I/O". There is a tablespace with about 30 separate data files that need to be "reorganized"!
Should we perform the reorganize before the migration or after on the new faster box?
What is the easiest way to do this for a newbie? Thanks.

Since your source and target platform all little ENDIAN format. Cold copy from OS level is fastest and easiest way.
If you plan to reorg the tablespace along the way, you have to do export/import, use data pump since you are on 10g.

Upgrade from 10gr2 SE to 10gr2 EP Verification

Is there anyway to tell if the catalog and catproc have been run after the upgrade?

when you use sqlplus connect to the server. it will show the version of database
or select * from v$version
It's not harmful to run catalog and catproc again. of course it takes time.

Migrating from Sql server get SQL Error: ORA-00936: missing expression

All,
I'm migrating from Sql Server to oracle 10g and I'm getting a
"SQL Error: ORA-00936: missing expression" error
when the following create table statement is executed. It appears 10g does not like the CREATE DEFAULT xxxx as xxx syntax. Any ideas??
CREATE TABLE EnvCapitalOtherCostAtom (
EnvID CHAR(36) NOT NULL,
CapitalID CHAR(36) NOT NULL,
Seq FLOAT DEFAULT
CREATE DEFAULT D_Set_To_Zero
     AS 0
NOT NULL,
AtomID CHAR(36) DEFAULT
CREATE DEFAULT D_NewGUID
     AS newid
NOT NULL,
AtomName VARCHAR2(100) NOT NULL,
AtomName_dqa NUMBER(5,0) DEFAULT
CREATE DEFAULT D_DQA_Dflt
     AS 10
NOT NULL,
CreatedOnTimeStamp TIMESTAMP(6) NOT NULL,
LastEditedOnTimeStamp TIMESTAMP(6) NOT NULL,
TFDubh_dqa NUMBER(5,0),
record_flags NUMBER(5,0) DEFAULT
CREATE DEFAULT D_Record_Flags
     AS 0
NOT NULL,
record_dqa NUMBER(5,0) DEFAULT
CREATE DEFAULT D_Record_DQA
     AS 30
NOT NULL
);

Hi Chris,
not sure SQL Server accepts the syntax you provided either. Even more I have checked MSDN(http://msdn2.microsoft.com/en-us/library/ms173565.aspx) and they recommend:
Avoid using CREATE DEFAULT in new development work, and plan to modify applications that currently use it. Instead, use default definitions created using the DEFAULT keyword of ALTER TABLE or CREATE TABLE. CREATE DEFAULT will be removed in a future version of Microsoft SQL Server.
In Oracle you should do the same either use DEFAULT in CREATE TABLE statement or in ALTER TABLE, have a look at http://download.oracle.com/docs/cd/B19306_01/appdev.102/b14251/adfns_constraints.htm#sthref626 for more details.
The proper Oracle syntax for your DDL should be something like:
CREATE TABLE EnvCapitalOtherCostAtom (
EnvID CHAR(36) NOT NULL,
CapitalID CHAR(36) NOT NULL,
Seq FLOAT DEFAULT 0 NOT NULL,
AtomID CHAR(36) DEFAULT SYS_GUID() NOT NULL,
AtomName VARCHAR2(100) NOT NULL,
AtomName_dqa NUMBER(5,0) DEFAULT 10 NOT NULL,
CreatedOnTimeStamp TIMESTAMP(6) NOT NULL,
LastEditedOnTimeStamp TIMESTAMP(6) NOT NULL,
TFDubh_dqa NUMBER(5,0),
record_flags NUMBER(5,0) DEFAULT 0 NOT NULL,
record_dqa NUMBER(5,0) DEFAULT 30 NOT NULL
);

CTAS in Exadata (11.2.0.3) from 10gR2*10.2.0.4) = ORA-03120

Similar Messages

Maybe you are looking for