ORA-00972 - when autoextending a datafile

Hi Guys,
I'm trying to help a client here that needs to put a datafile in auto extend, and when he typed the code he gets this error:
ORA-00972: identifier is too long
Can someone help please?
Regards,
Texas!

Hi again!
That is a very strange problem. It looks like that the problem is a system table with an identifier > 30 characters. In Oracle each identified can only have a maximum of 30 characters. If an identifier is too long ORA-00972 is thrown. This topic is discussed at the following page:
[http://www.dba-oracle.com/sf_ora_00972_identifier_is_too_long.htm]
Unfortunately they have posted no solution to this on the above page.
regards
Edited by: Florian W. on 05.03.2009 14:17
Hi once again!
You may also look here:
[http://www.kuzbass.ru:8086/docs/rdb702/sqlnet/natconn/instab.htm]
In section A.3 Handling 31-Character Object Names this problem is also discussed.
regards again

Similar Messages

ORA 1426 when dropping a datafile.

Hello,
While dropping a datafile, I got the following error message:
ORA-00604: une erreur s'est produite au niveau SQL récursif 1
ORA-01426: dépassement numérique
The command I used is the following:
alter tablespace m4prod drop datafile 'd:\oradata\paie\m4prod02.dbf';
Most of the posts I got from the net regarding that error were in reference to calling a procedure. I am not invoking any PL/SQL block so I don't understand why that error and how do I fix it.
Thanks in advance.

My database version is:
select from v$version;*
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
PL/SQL Release 10.2.0.1.0 - Production
CORE 10.2.0.1.0 Production
TNS for 32-bit Windows: Version 10.2.0.1.0 - Production
NLSRTL Version 10.2.0.1.0 - Production
I did not configure any trigger either on the database nor on an object.

ORA-3297 when attempting to resize a datafile to a small size

Hello,
I have a tablespace tbspace_A which has 3 datafiles. There are numerous segments in tbspace_A. This tablespace grew to 80 gigs while lots of inserts were performed on tables. Now those tables are either dropped or have records deleted dramatically. Now I want to reduce the tablespace from 80 gigs to 50 gigs so I can return the unused space to the o/s. I am getting error ORA-3297 when trying to reduce a datafile /oradata/tbspace_A03.dbf belong to tbspace_A.
My task now is to:
1) Find the segments that occupy /oradata/tbspace_A03.dbf datafile
2) alter table table_name99 move tablespace scratch_tbspace;
3) alter table table_name99 move tbspace_A;
4) Attemp again to resize(smaller) the /oradata/tbspace_A03.dbf
so to return disk space to the o/s.
Is this the correct method?
Is there a better method?
What are the gotchas?
Thank you.

This is the procedure to follow, the gotchas I see are:
1. Watch out for relational constraints
2. Rebuild indexes afterwards
3. You may use the move command, unless the table has LONG/LONG RAW columns.
You could use Enterprise Manager and/or oracle expdp/impdp to perform the remapping tasks (10g).
~ Madrid

ORA-01152 when restoring from RMAN backupset in NOARCHIVELOG mode

Hi all,
I got the error ORA-01152 when I tried restoring an Oracle 10g R1 database from an RMAN backupset into a new server. The error returned when it reached to the level of opening the database in resetlogs.
The database runs on NOARCHIVELOG mode and on Windows 2003 Server SP2 32-bit.
Following is what I did in RMAN:
set ORACLE_HOME=D:\oracle\product\10.1.0\db_1
set ORACLE_SID=DAWA
set PATH=D:\oracle\product\10.1.0\db_1\bin;%PATH%
cd %ORACLE_HOME%\bin
rman target sys/mypassword
Recovery Manager: Release 10.2.0.1.0 - Production on Tue Feb 13 00:36:55 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database (not started)
RMAN> startup nomount pfile=X:\temp\DawaPFILE.ORA
connected to target database (not started)
Oracle instance started
Total System Global Area 1048576000 bytes
Fixed Size 792200 bytes
Variable Size 551807352 bytes
Database Buffers 494927872 bytes
Redo Buffers 1048576 bytes
RMAN> restore controlfile from
'X:\temp\Flash_Rec\DAWA\AUTOBACKUP\2011_07_16\O1_
MF_S_756655133_7226R018_.BKP';
Starting restore at 19-JUL-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=270 devtype=DISK
channel ORA_DISK_1: restoring controlfile
channel ORA_DISK_1: restore complete
output filename=D:\ORACLE\ORADATA\DAWA\CONTROL01.CTL
output filename=D:\ORACLE\ORADATA\DAWA\CONTROL02.CTL
output filename=D:\ORACLE\ORADATA\DAWA\CONTROL03.CTL
Finished restore at 17-AUG-11
alter database mount;
database mounted
catalog backuppiece 'X:\temp\PUMHJATD_1_1';
catalog backuppiece 'X:\temp\PTMHJ91Q_1_1';
/* Rename the Redologfiles,so that they can be created in new locations
the database is opened in resetlogs */
SQL>conn sys as sysdba
-- get registered files from SELECT * FROM V$LOGFILE
SQL> alter database rename file
'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO01.LOG' to
'X:\oracle\oradata\dawa\REDO01.LOG';
alter database rename file 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO02.LOG'
to 'X:\oracle\oradata\dawa\REDO02.LOG';
alter database rename file 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO03.LOG'
to 'X:\oracle\oradata\dawa\REDO03.LOG';
alter database rename file 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO04.LOG'
to 'X:\oracle\oradata\dawa\REDO04.LOG';
alter database rename file 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO05.LOG'
to 'X:\oracle\oradata\dawa\REDO05.LOG';
alter database rename file 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO06.LOG'
to 'X:\oracle\oradata\dawa\REDO06.LOG';
alter database rename file 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO07.LOG'
to 'X:\oracle\oradata\dawa\REDO07.LOG';
/* Now in RMAN: restore the datafiles
    to new locations and recover. */
RMAN> run{
set newname for datafile
'E:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\UNDOTBS201' TO
'D:\oracle\oradata\dawa\UNDOTBS201';
set newname for datafile
'E:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\UNDOTBS202' TO
'D:\oracle\oradata\dawa\UNDOTBS202';
restore database;
switch datafile all;
alter database open resetlogs;
.../* alter database open resetlogs returned the errors: */
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of alter db command at 08/18/2011 08:44:45
ORA-01152: file 2 was not restored from a sufficiently old backup
ORA-01110: data file 2: 'D:\ORACLE\ORADATA\DAWA\UNDOTBS206'Thanks in advance.

SYS @ DAWA> shutdown immediate
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
SYS @ DAWA> startup mount
ORACLE instance started.
Total System Global Area 1048576000 bytes
Fixed Size                   792200 bytes
Variable Size             551807352 bytes
Database Buffers          494927872 bytes
Redo Buffers                1048576 bytes
Database mounted.
SYS @ DAWA> recover database using backup controlfile until cancel;
ORA-00279: change 329012 generated at 03/08/2005 16:24:46 needed for thread 1
ORA-00289: suggestion :
X:\ORACLE\ORADATA\FLASH_REC\DAWA\ARCHIVELOG\2011_08_18\O1_MF_1_6_%U_.ARC
ORA-00280: change 329012 for thread 1 is in sequence #6
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00308: cannot open archived log
'X:\ORACLE\ORADATA\FLASH_REC\DAWA\ARCHIVELOG\2011_08_18\O1_MF_1_6_%U_.ARC'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: 'X:\ORACLE\ORADATA\DAWA\SYSTEM01.DBF'You can download the alert log from here:
http://ahmedbaraka.com/temp/alertdawa.log

IMPDP SQLFILE : multibyte characters in constraint_name leads to ORA-00972

Hi,
I'm actually dealing with constraint_name made of multibyte characters (for example : constrain_name='VALIDA_CONFIRMAÇÃO_PREÇO13').
Of course this Bad Idea® is inherited (I'm against all the fancy stuff like éàù in filenames and/or directories on my filesystem....)
The scenario is as follows :
0 - I'm supposed to do a "remap_schema". Everything in the schema SCOTT should now be in a schema NEW_SCOTT.
1 - The scott schema is exported via datapump
2 - I do an impdp with SQLFILE in order to get all the DDL (table, packages, synonyms, etc...)
3 - I do some sed on the generated sqlfile to change every occurence of SCOTT to NEW_SCOTT (this part is OK)
4 - Once the modified sqlfile is executed, I do an impdp with DATA_ONLY.
(The scenario was imagined from this thread : {message:id=10628419} )
I'm getting some ORA-00972: identifier is too long at step 4 when executing the sqlfile.
I see that some DDL for constraint creation in the file (generated at step#2) is written as follow :ALTER TABLE "TW_PRI"."B_TRANSC" ADD CONSTRAINT "VALIDA_CONFIRMAÃÃO_PREÃO14" CHECK ...Obviously, the original name of the constraint with cedilla and tilde gets translated to something else which is longer than 30 char/byte...
As the original name is from Brazil, I also tried do add an EXPORT LANG=pt_BR.UTF-8 in my script before running the impdp for sqlfile. This didn't change anything. (the original $LANG is en_US.UTF-8)
In order to create a testcase for this thread, I tried to reproduce on my sandbox database... but, there, I don't have the issue. :-(
The real system is an 4-nodes database on Exadata (11.2.0.3) with NLS_CHARACTERSET=AL32UTF8.
My sandbox database is a (nonRAC) 11.2.0.1 on RHEL4 also AL32UTF8.
The constraint_name is the same on both system : I checked byte by byte using DUMP() on the constraint_name.
Feel free to shed any light and/or ask for clarification if needed.
Thanks in advance for those who'll take on their time to read all this.
I decided to include my testcase from my sandbox database, even if it does NOT reproduce the issue +(maybe I'm missing something obvious...)+
I use the following files.
- createTable.sql :$ cat createTable.sql
drop table test purge;
create table test
(id integer,
val varchar2(30));
alter table test add constraint VALIDA_CONFIRMAÇÃO_PREÇO13 check (id<=10000000000);
select constraint_name, lengthb(constraint_name) lb, lengthc(constraint_name) lc, dump(constraint_name) dmp
from user_constraints where table_name='TEST';- expdpTest.sh :$ cat expdpTest.sh
expdp scott/tiger directory=scottdir dumpfile=testNonAscii.dmp tables=test- impdpTest.sh :$ cat impdpTest.sh
impdp scott/tiger directory=scottdir dumpfile=testNonAscii.dmp sqlfile=scottdir:test.sqlfile.sql tables=testThis is the run :
[oracle@Nicosa-oel test_nonAsciiColName]$ sqlplus scott/tiger
SQL*Plus: Release 11.2.0.1.0 Production on Tue Feb 12 18:58:27 2013
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> @createTable
Table dropped.
Table created.
Table altered.
CONSTRAINT_NAME                  LB       LC
DMP
VALIDA_CONFIRMAÇÃO_PREÇO13             29         26
Typ=1 Len=29: 86,65,76,73,68,65,95,67,79,78,70,73,82,77,65,195,135,195,131,79,95
,80,82,69,195,135,79,49,51
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
[oracle@Nicosa-oel test_nonAsciiColName]$ ./expdpTest.sh
Export: Release 11.2.0.1.0 - Production on Tue Feb 12 19:00:12 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Starting "SCOTT"."SYS_EXPORT_TABLE_01": scott/******** directory=scottdir dumpfile=testNonAscii.dmp tables=test
Estimate in progress using BLOCKS method...
Processing object type TABLE_EXPORT/TABLE/TABLE_DATA
Total estimation using BLOCKS method: 0 KB
Processing object type TABLE_EXPORT/TABLE/TABLE
Processing object type TABLE_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
. . exported "SCOTT"."TEST"                                  0 KB       0 rows
Master table "SCOTT"."SYS_EXPORT_TABLE_01" successfully loaded/unloaded
Dump file set for SCOTT.SYS_EXPORT_TABLE_01 is:
/home/oracle/scott_dir/testNonAscii.dmp
Job "SCOTT"."SYS_EXPORT_TABLE_01" successfully completed at 19:00:22
[oracle@Nicosa-oel test_nonAsciiColName]$ ./impdpTest.sh
Import: Release 11.2.0.1.0 - Production on Tue Feb 12 19:00:26 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Master table "SCOTT"."SYS_SQL_FILE_TABLE_01" successfully loaded/unloaded
Starting "SCOTT"."SYS_SQL_FILE_TABLE_01": scott/******** directory=scottdir dumpfile=testNonAscii.dmp sqlfile=scottdir:test.sqlfile.sql tables=test
Processing object type TABLE_EXPORT/TABLE/TABLE
Processing object type TABLE_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
Job "SCOTT"."SYS_SQL_FILE_TABLE_01" successfully completed at 19:00:32
[oracle@Nicosa-oel test_nonAsciiColName]$ cat scott_dir/test.sqlfile.sql
-- CONNECT SCOTT
ALTER SESSION SET EVENTS '10150 TRACE NAME CONTEXT FOREVER, LEVEL 1';
ALTER SESSION SET EVENTS '10904 TRACE NAME CONTEXT FOREVER, LEVEL 1';
ALTER SESSION SET EVENTS '25475 TRACE NAME CONTEXT FOREVER, LEVEL 1';
ALTER SESSION SET EVENTS '10407 TRACE NAME CONTEXT FOREVER, LEVEL 1';
ALTER SESSION SET EVENTS '10851 TRACE NAME CONTEXT FOREVER, LEVEL 1';
ALTER SESSION SET EVENTS '22830 TRACE NAME CONTEXT FOREVER, LEVEL 192 ';
-- new object type path: TABLE_EXPORT/TABLE/TABLE
CREATE TABLE "SCOTT"."TEST"
   (     "ID" NUMBER(*,0),
     "VAL" VARCHAR2(30 BYTE)
   ) SEGMENT CREATION DEFERRED
PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 COMPRESS FOR OLTP LOGGING
TABLESPACE "MYTBSCOMP" ;
-- new object type path: TABLE_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
ALTER TABLE "SCOTT"."TEST" ADD CONSTRAINT "VALIDA_CONFIRMAÇÃO_PREÇO13" CHECK (id<=10000000000) ENABLE;I was expecting to have the cedilla and tilde characters displayed incorrectly....
Edited by: Nicosa on Feb 12, 2013 7:13 PM

Srini Chavali wrote:
If I understand you correctly, you are unable to reproduce the issue in the test instance, while it occurs in the production instance. Is the "schema move" being done on the same database - i.e. you are "moving" from SCOTT to NEW_SCOTT on the same database (test to test, and prod to prod) ? Do you have to physically move/copy the dmp file ? Hi Srini,
On the real system, the schema move will be to and from different machines (but same DBversion).
I'm not doing the real move for the moment, just trying to validate a way to do it, but I guess it's important to say that the dump being used for the moment comes from the same database (the long story being that due to some column using object datatype which caused error in the remap, I had to reload the dump with the "schema rename", drop the object column, and recreate a dump file without the object_datatype...).
So Yes, the file will have to move, but in the current test, it doesn't.
Srini Chavali wrote:
Obviously something is different in production than test - can you post the output of this command from both databases ?
SQL> select * from NLS_DATABASE_PARAMETERS;
Yes Srini, something is obviously different : I'm starting to think that the difference might be in the Linux/shell side rather than on the impdp as datapump is supposed to be NLS_LANG/CHARSET-proof +(when traditional imp/exp was really sensible on those points)+
The result on the Exadata where I have the issue :PARAMETER                      VALUE
NLS_LANGUAGE                   AMERICAN
NLS_TERRITORY                  AMERICA
NLS_CURRENCY                   $
NLS_ISO_CURRENCY               AMERICA
NLS_NUMERIC_CHARACTERS         .,
NLS_CHARACTERSET               AL32UTF8
NLS_CALENDAR                   GREGORIAN
NLS_DATE_FORMAT                DD-MON-RR
NLS_DATE_LANGUAGE              AMERICAN
NLS_SORT                       BINARY
NLS_TIME_FORMAT                HH.MI.SSXFF AM
NLS_TIMESTAMP_FORMAT           DD-MON-RR HH.MI.SSXFF AM
NLS_TIME_TZ_FORMAT             HH.MI.SSXFF AM TZR
NLS_TIMESTAMP_TZ_FORMAT        DD-MON-RR HH.MI.SSXFF AM TZR
NLS_DUAL_CURRENCY              $
NLS_COMP                       BINARY
NLS_LENGTH_SEMANTICS           BYTE
NLS_NCHAR_CONV_EXCP            FALSE
NLS_NCHAR_CHARACTERSET         AL16UTF16
NLS_RDBMS_VERSION              11.2.0.3.0the result on my sandbox DB :PARAMETER                      VALUE
NLS_LANGUAGE                   AMERICAN
NLS_TERRITORY                  AMERICA
NLS_CURRENCY                   $
NLS_ISO_CURRENCY               AMERICA
NLS_NUMERIC_CHARACTERS         .,
NLS_CHARACTERSET               AL32UTF8
NLS_CALENDAR                   GREGORIAN
NLS_DATE_FORMAT                DD-MON-RR
NLS_DATE_LANGUAGE              AMERICAN
NLS_SORT                       BINARY
NLS_TIME_FORMAT                HH.MI.SSXFF AM
NLS_TIMESTAMP_FORMAT           DD-MON-RR HH.MI.SSXFF AM
NLS_TIME_TZ_FORMAT             HH.MI.SSXFF AM TZR
NLS_TIMESTAMP_TZ_FORMAT        DD-MON-RR HH.MI.SSXFF AM TZR
NLS_DUAL_CURRENCY              $
NLS_COMP                       BINARY
NLS_LENGTH_SEMANTICS           BYTE
NLS_NCHAR_CONV_EXCP            FALSE
NLS_NCHAR_CHARACTERSET         AL16UTF16
NLS_RDBMS_VERSION              11.2.0.1.0------
Richard Harrison . wrote:
Hi,
Did you set NLS_LANG also when you did the import?Yes, that is one of the difference between the Exadata and my sandbox.
My environnement in sandbox has NLS_LANG=AMERICAN_AMERICA.AL32UTF8 where the Exadata doesn't have the variable set.
I tried to add it, but it didn't change anything.
Richard Harrison . wrote:
Also not sure why you are doing the sed part? Do you have hard coded scheme references inside some of the plsql?Yes, that is why I choose to sed. The (ugly) code have :
- Procedures inside the same package that references one another with the schema prepended
- Triggers with PL/SQL codes referencing tables with schema prepended
- Dynamic SQL that "builds" queries with schema prepended
- Object Type that does some %ROWTYPE on tables with schema prepended (that will be solved by dropping the column based on those types as they obviously are not needed...)
- Data model with object whose names uses non-ascii characters
+(In France we use to call this "gas power plant" in order to tell how a mess it is : pipes everywhere going who-knows-where...)+
The big picture is that this kind of "schema move & rename" should be as automatic as possible, as the project is to actually consolidate several existing databases on the Exadata :
One schema for each country, hence the rename of the schemas to include country-code.
I actually have a workaround yet : Rename the objects that have funky characters in their name before doing the export.
But I was curious to understand why the SQLFILE messed up the constraint_name on one sustem when it doesn't on another...

Column alias results in ORA-00972

Hi,
I am using Eclipselink v1.0.2 on glassfish.
I have a query where I have set the maxResults to 1 like so:
this.entityManager.createQuery("SELECT t FROM Tbl t where t.name='271040300018**'")
                    .setMaxResults(1)
                    .getResultList();
The resultant query contains a column alias that has more than 30 characters which causes an ORA-00972 error. I've noticed that if I don't call setMaxResults the query does not contain aliased column names. Is there a way to either make sure that the query generator does not generate invalid column names or get it to not alias columns when I have a result set limit?
Thanks,
Drew
Edited by: user10816727 on Jan 27, 2009 1:02 PM

Here is the generated query with the problematic aliases bolded. Note that I cannot change the length of the non aliased column names as a workaround.
Thanks,
Drew
SELECT * FROM (SELECT /*+ FIRST_ROWS */ a.*, ROWNUM rnum FROM (SELECT new_drug_status AS new_drug_status1, message AS message2, message_stop_date AS message_stop_date3, termination_date AS termination_date4, cms_drug_status AS cms_drug_status5, drug_status_ovrd AS drug_status_ovrd6, min_rx_qty AS min_rx_qty7, max_rx_qty AS max_rx_qty8, min_rx_days AS min_rx_days9, max_rx_days AS max_rx_days10, max_dose AS max_dose11, min_age AS min_age12, max_age AS max_age13, min_age_dob_opt AS min_age_dob_opt14, max_age_dob_opt AS max_age_dob_opt15, sex_restriction AS sex_restriction16, qty_dsup_compare_rule AS qty_dsup_compare_rule17, max_qty_over_time AS max_qty_over_time18, rx_qty_opt_multiplier AS rx_qty_opt_multiplier19, specialty_drug_ind AS specialty_drug_ind20, ssb_copay_tier AS ssb_copay_tier21, msb_copay_tier AS msb_copay_tier22, bga_copay_tier AS bga_copay_tier23, gen_copay_tier AS gen_copay_tier24, bng_sngl_inc_exc_ind AS bng_sngl_inc_exc_ind25, bng_multi_inc_exc_ind AS bng_multi_inc_exc_ind26, bga_inc_exc_ind AS bga_inc_exc_ind27, gen_inc_exc_ind AS gen_inc_exc_ind28, merge_defaults AS merge_defaults29, otc_chk_flag AS otc_chk_flag30, physician_list AS physician_list31, physician_specialty_list AS physician_specialty_list32, alternate_price_schedule AS alternate_price_schedule33, alternate_copay_sched AS alternate_copay_sched34, max_rxs_patient AS max_rxs_patient35, max_rxs_time_flag AS max_rxs_time_flag36, copay_network_ovrd AS copay_network_ovrd37, max_days_supply_opt AS max_days_supply_opt38, max_days_over_time AS max_days_over_time39, reject_only_msg_flag AS reject_only_msg_flag40, max_qty_per_fill AS max_qty_per_fill41, days_supply_opt_multiplier AS days_supply_opt_multiplier42, recalc_price_schedule AS recalc_price_schedule43, alternate_pricing_strategy AS alternate_pricing_strategy44, alternate_copay_strategy AS alternate_copay_strategy45, max_days_over_time_drug_list AS max_days_over_time_drug_list46, max_qty_over_time_drug_list AS max_qty_over_time_drug_list47, max_rxs_patient_drug_list AS max_rxs_patient_drug_list48, max_price_patient_drug_list AS max_price_patient_drug_list49, max_rxs_time_flag_mult AS max_rxs_time_flag_mult50, max_price_patient AS max_price_patient51, max_price_time_flag AS max_price_time_flag52, max_price_patient_opt AS max_price_patient_opt53, max_price_patient_split_opt AS max_price_patient_split_opt54, max_price_patient_pricing_opt AS max_price_patient_pricing_opt55, max_price_patient_split_copay AS max_price_patient_split_copay56, max_price_patient_copay AS max_price_patient_copay57, misc_data_1 AS misc_data_158, misc_data_2 AS misc_data_259, misc_data_3 AS misc_data_360, misc_data_4 AS misc_data_461, misc_data_5 AS misc_data_562, user_id_created AS user_id_created63, gpi_exception_list AS gpi_exception_list64, pharmacy_country_code AS pharmacy_country_code65, generic_product_id AS generic_product_id66, pharmacy_state AS pharmacy_state67, effective_date AS effective_date68, process_rule AS process_rule69, apply_on_group_renewal_ind AS apply_on_group_renewal_ind70 FROM PHIDBA.gpi_exception_lists WHERE (generic_product_id = ?)) a WHERE ROWNUM <= ?) WHERE rnum > ?
     bind => [271040300018**, 1, 0]

Oracle Connectivity with MS SQL Server. ORA-00972: identifier is too long

I have linked Oracle Database with MS SQL Server using HS and DB Link.
DB Link Script:
CREATE DATABASE LINK "FCHH"
CONNECT TO SA
IDENTIFIED BY <PWD>
USING 'LISTENER_FCHH';
Links tested successfully.
Now "SA" user in Microsoft SQL Server has multiple databases i.e. Master,SecurePerfect,SecurePerfectHistory. when I try following command
select * from "SecurePerfectHistory.DBO.BadgeHistoryTable"@FCHH
ORA-00972: identifier is too long

ORA-00972: identifier is too long
Cause: An identifier with more than 30 characters was specified.
Action: Specify at most 30 charactersAman....

ORA-01516: nonexistent log file, datafile, or tempfile

Hi,
in 10g R2 on Win XP when I do :
alter database rename file 'C:\oracle\oradata\ORCL\USERS01.DBF' to 'C:\oracle\oradata\ORCL2\USERS01.DBF';
I receive :
ORA-01511: fail to change name ...
ORA-01516: nonexistent log file, datafile, or tempfile
'C:\oracle\oradata\ORCL\USERS01.DBF'
But it realy exists.
Please help.

Hi,
I'm comming back now.
Before putting offline the data files, I tried with log file (since to duplicate database I should rename all (see the below script) but :
SQL> alter database rename file 'C:\oracle\oradata\orcl\REDO01.LOG' to 'C:\oracle\oradata\ORCL2\REDO01.LOG';
alter database rename file 'C:\oracle\oradata\orcl\REDO01.LOG' to 'C:\oracle\oradata\ORCL2\REDO01.LOG'
ORA-01516: nonexistent log file, datafile, or tempfile
'C:\oracle\oradata\orcl\REDO01.LOG'
Can we put a log file off line ?
Thank you.
My script :
alter database rename file     'C:\oracle\oradata\orcl\EXAMPLE01.DBF'     to     'C:\oracle\oradata\ORCL2\EXAMPLE01.DBF';
alter database rename file     'C:\oracle\oradata\orcl\REDO01.LOG'     to     'C:\oracle\oradata\ORCL2\REDO01.LOG';
alter database rename file     'C:\oracle\oradata\orcl\REDO02.LOG'     to     'C:\oracle\oradata\ORCL2\REDO02.LOG';
alter database rename file     'C:\oracle\oradata\orcl\REDO03.LOG'     to     'C:\oracle\oradata\ORCL2\REDO03.LOG';
alter database rename file     'C:\oracle\oradata\orcl\REDO04.LOG'     to     'C:\oracle\oradata\ORCL2\REDO04.LOG';
alter database rename file     'C:\oracle\oradata\orcl\SYSAUX01.DBF'     to     'C:\oracle\oradata\ORCL2\SYSAUX01.DBF';
alter database rename file     'C:\oracle\oradata\orcl\SYSTEM01.DBF'     to     'C:\oracle\oradata\ORCL2\SYSTEM01.DBF';
alter database rename file     'C:\oracle\oradata\orcl\TEMP01.DBF'     to     'C:\oracle\oradata\ORCL2\TEMP01.DBF';
alter database rename file     'C:\oracle\oradata\orcl\UNDOTBS01.DBF'     to     'C:\oracle\oradata\ORCL2\UNDOTBS01.DBF';
alter database rename file     'C:\oracle\oradata\orcl\USERS01.DBF'     to     'C:\oracle\oradata\ORCL2\USERS01.DBF';
Any way I put USER01.DBF off line on sourcr (orcl) :
SQL> alter database datafile 'C:\ORACLE\ORADATA\ORCL\USERS01.DBF' offline;
But again :
SQL> alter database rename file 'C:\oracle\oradata\orcl\USERS01.DBF' to 'C:\oracle\oradata\ORCL2\USERS01.DBF';
alter database rename file 'C:\oracle\oradata\orcl\USERS01.DBF' to 'C:\oracle\oradata\ORCL2\USERS01.DBF'
ORA-01516: nonexistent log file, datafile, or tempfile
'C:\oracle\oradata\orcl\USERS01.DBF'
Message was edited by:
user522961

PHP - Load Gif image into Oracle Blob field - ORA-00972 error

I am receiving an " ORA-00972 - Identifier Is too Long" error message when I try to update a BLOB field with file contents from a gif file.
__GIF FILES_:_
c:\bl\x_PageLayout-4_LA.gif (15K)
c:\bl\x_PageLayout-4_Spec.gif (21k)
===================================================================================================================================
ORACLE DATABASE (STYLEELEMENTPIX TABLE):*
STYLE_ID NUMBER
SEQ_KEY NUMBER
PIX_NAME VARCHAR2(30 BYTE)
PIX BLOB
PIX_LABEL VARCHAR2(30 BYTE)
MODIFY_DATE DATE
PIX_TYPE CHAR(1 BYTE)
DEFAULTDISPLAY CHAR(1 BYTE)
PIX field currently is null
===================================================================================================================================
PHP CODE:*
$filename = 'C:\BL\\';
$filename .= $row->PIX_NAME; //filename of gif ex: c:\bl\x_PageLayout-4_LA.gif
$fp = fopen($filename, "rb"); //open gif file
$file_content = fread($fp, filesize($filename)); //read gif file
//set gif file in PIX field (PIX datatyle BLOB)
$cursor1 = oci_parse($conn, "UPDATE STYLEELEMENTPIX SET PIX = '$file_content' WHERE STYLE_ID = $row->STYLE_ID AND SEQ_KEY = $row->SEQ_KEY");
oci_execute ($cursor1);
For both records, style id will be 100 ($row->STYLE_ID), and seq_key will be 1 for the first record and 2 for the second ($row->SEQ_KEY)
===================================================================================================================================
ERROR MESSAGE:
Warning: oci_parse() [function.oci-parse]: ORA-00972: identifier is too long in C:\wamp\www\eStyleGuide\Admin\BLOB.php on line 44 ($cursor1 = ....)

Use a LOB locator. See "Inserting and Updating LOBs" on p 193 of the free book http://www.oracle.com/technetwork/topics/php/underground-php-oracle-manual-098250.html
A more concerning issue is the security implications of using string concatenation to construct the SQL statement. It is recommended to use bind variables.

ORA-00972 from generated piece of SQL code

Hi - I stepped over this problem while testing a new procedure:
7 WHENEVER SQLERROR exit
8 SELECT 'STOP! Missing refresh group!' " ' FROM DUAL
9 WHERE NOT EXISTS (SELECT refg_name FROM SYS.DBA_REFRESH WHERE rname='Thingy')
10 SELECT 1/(sign(count(*)) FROM (SELECT refg_name FROM SYS.DBA_REFRESH WHERE rname ='Thingy')
I always get an ORA-00972: identifier is too long when I try to run these lines.
But WHERE is there a too long identifier? "STOP! Missing refresh group!" is only 28 characters long.
Somebody got a clue?
Thanks in advance,
Thomas

The suspection is what you are using something like
SQL> SELECT "'STOP! Missing refresh group!' " FROM DUAL
2 /
SELECT "'STOP! Missing refresh group!' " FROM DUAL
ERROR at line 1:
ORA-00972: identifier is too long, isn't it ?
Double-quoted strings are identifiers - and can't have more than 30 symbols.
Use single quotation in strings.
Rgds.

ORA-01516: nonexistent log file, datafile, or tempfile _2

Hi,
I'm following what is here :
Scenario 1: Creating a Standby Database on the Same Host
http://www.mid.main.vsu.ru/docs/oracle/server.816/a76995/standbys.htm#29841
When issuing :
SQL> alter database rename file 'C:\oracle\oradata\orcl\USERS01.DBF' to 'C:\oracle\oradata\ORCL2\USERS01.DBF';
ORA-01516: nonexistent log file, datafile, or tempfile
'C:\oracle\oradata\orcl\USERS01.DBF'
I put 'C:\oracle\oradata\orcl\USERS01.DBF' offline but it was the same;
Any solution please ?
Thank you.

yes it was.
on ORCL :
SQL> select file_name from dba_data_files;
FILE_NAME
C:\ORACLE\ORADATA\ORCL\USERS01.DBF
C:\ORACLE\ORADATA\ORCL\SYSAUX01.DBF
C:\ORACLE\ORADATA\ORCL\UNDOTBS01.DBF
C:\ORACLE\ORADATA\ORCL\SYSTEM01.DBF
C:\ORACLE\ORADATA\ORCL\EXAMPLE01.DBF
on orcl2
SQL> alter database rename file 'C:\oracle\oradata\orcl\EXAMPLE01.DBF' to 'C:\oracle\oradata\ORCL2\EXAMPLE01.DBF';
alter database rename file 'C:\oracle\oradata\orcl\EXAMPLE01.DBF' to 'C:\oracle\oradata\ORCL2\EXAMPLE01.DBF'
ORA-01516: nonexistant
'C:\oracle\oradata\orcl\EXAMPLE01.DBF'
Message was edited by:
user522961

ORA-01180: can not create datafile 1 during RMAN restore.

Hello,
I am trying to refresh one of our QA environments and I am getting this error message:
RMAN> run
2> {
3> allocate channel c1 device type disk;
4> allocate channel c2 device type disk;
5> restore database;
6> recover database;
7> }
allocated channel: c1
channel c1: SID=5 device type=DISK
allocated channel: c2
channel c2: SID=131 device type=DISK
Starting restore at 08-NOV-12
using channel ORA_DISK_1
creating datafile file number=1 name=+DATA1/alephpr/datafile/system.269.722874729
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 11/08/2012 16:27:40
ORA-01180: can not create datafile 1
ORA-01110: data file 1: '+DATA1/alephpr/datafile/system.269.722874729' I created a new database from scratch with the same name as is in Production, later on I will proceed to rename it to the right one. I started the steps for refreshing the PRD copy:
RMAN> shutdown immediate
using target database control file instead of recovery catalog
database dismounted
Oracle instance shut down
RMAN> startup nomount
connected to target database (not started)
Oracle instance started
Total System Global Area 534462464 bytes
Fixed Size 2228200 bytes
Variable Size 176160792 bytes
Database Buffers 348127232 bytes
Redo Buffers 7946240 bytes
RMAN> set dbid=3573460394
executing command: SET DBID
RMAN> restore controlfile from '/restorealeph/c-3573460394-20121106-01';
Starting restore at 08-NOV-12
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=130 device type=DISK
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:07
+output file name=+DATA1/alephpr/controlfile/current.260.798747585+
+output file name=+FLASH/alephpr/controlfile/current.276.798747585+
Finished restore at 08-NOV-12
RMAN> alter database mount;
database mounted
released channel: ORA_DISK_1Once the control file is restored, I need to crosscheck, delete expired and catalog the backups at the new server:
RMAN> crosscheck backup;
Crosschecked 48 objects
RMAN> delete noprompt expired backup;
Deleted 48 EXPIRED objects
RMAN> list backup summary;
specification does not match any backup in the repositoryI need now to catalog the backups we transferred from Prod into the QA server's directory /restorealeph:
RMAN> catalog start with '/restorealeph/';
searching for all files that match the pattern /restorealeph/
List of Files Unknown to the Database
=====================================
File Name: /restorealeph/9cnpm51u_1_1
File Name: /restorealeph/9enpm6lj_1_1
File Name: /restorealeph/c-3573460394-20121107-00
File Name: /restorealeph/c-3573460394-20121107-01
File Name: /restorealeph/c-3573460394-20121106-01
Do you really want to catalog the above files (enter YES or NO)? YES
cataloging files...
cataloging done
List of Cataloged Files
=======================
File Name: /restorealeph/9cnpm51u_1_1
File Name: /restorealeph/9enpm6lj_1_1
File Name: /restorealeph/c-3573460394-20121107-00
File Name: /restorealeph/c-3573460394-20121107-01
File Name: /restorealeph/c-3573460394-20121106-01
RMAN> list backup summary;
List of Backups
===============
Key     TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
4097    B F A DISK        07-NOV-12       1       1       NO         BACKUP_ALEPHPR.TUR_110712030000
4098    B A A DISK        07-NOV-12       1       1       NO         BACKUP_ALEPHPR.TUR_110712030000
RMAN> list backup tag="BACKUP_ALEPHPR.TUR_110712030000";
List of Backup Sets
===================
BS Key Type LV Size       Device Type Elapsed Time Completion Time
4097    Full    178.04G    DISK        00:00:00     07-NOV-12
        BP Key: 4097   Status: AVAILABLE Compressed: NO Tag: BACKUP_ALEPHPR.TUR_110712030000
        Piece Name: /restorealeph/9cnpm51u_1_1
List of Datafiles in backup set 4097
File LV Type Ckp SCN    Ckp Time Name
1       Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/system.269.722874729
2       Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/sysaux.266.722874731
3       Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/undotbs1.289.722874727
4       Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/undotbs2.257.722874727
5       Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/users.298.722874731
6       Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/audit.299.723372305
7       Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/case_datos.260.723372307
8       Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/case_indices.261.723372307
9       Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/data_hist.262.723372309
10      Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/data_l.264.723372319
11      Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/data_long.265.723372349
12      Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/data_md.270.723372355
13      Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/data_sm.271.723372369
14      Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/data_xl.272.723372375
15      Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/index_l.273.723372401
16      Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/index_md.274.723372427
17      Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/index_sm.275.723372455
18      Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/index_xl.276.723372473
19      Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/tools.278.723372501
26      Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/data_sm.300.736088959
27      Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/dev_disco_ptm5_meta.301.746385117
28      Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/dev_disco_pstore.302.746385119
29      Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/dev_disco_ptm5_cache.304.746385121
30      Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/undotbs1.305.796391931
31      Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/undotbs2.306.796392185
BS Key Size       Device Type Elapsed Time Completion Time
4098    16.89G     DISK        00:00:00     07-NOV-12
        BP Key: 4098   Status: AVAILABLE Compressed: NO Tag: BACKUP_ALEPHPR.TUR_110712030000
        Piece Name: /restorealeph/9enpm6lj_1_1
List of Archived Logs in backup set 4098
Thrd Seq     Low SCN    Low Time Next SCN   Next Time
1    35722   6919870864350 06-NOV-12 6919871887697 06-NOV-12
1    35723   6919871887697 06-NOV-12 6919872372211 06-NOV-12
1    35724   6919872372211 06-NOV-12 6919872410158 06-NOV-12
1    35725   6919872410158 06-NOV-12 6919872447301 06-NOV-12
1    35726   6919872447301 06-NOV-12 6919872503332 06-NOV-12
1    35727   6919872503332 06-NOV-12 6919872551564 06-NOV-12
1    35728   6919872551564 06-NOV-12 6919872603881 06-NOV-12
1    35729   6919872603881 06-NOV-12 6919872655942 06-NOV-12
1    35730   6919872655942 06-NOV-12 6919872698722 06-NOV-12
1    35731   6919872698722 06-NOV-12 6919872741655 06-NOV-12
1    35732   6919872741655 06-NOV-12 6919872782284 06-NOV-12
1    35733   6919872782284 06-NOV-12 6919872872302 06-NOV-12
1    35734   6919872872302 06-NOV-12 6919872910206 06-NOV-12
1    35735   6919872910206 06-NOV-12 6919872945577 06-NOV-12
1    35736   6919872945577 06-NOV-12 6919872980056 06-NOV-12
1    35737   6919872980056 06-NOV-12 6919873013411 06-NOV-12
1    35738   6919873013411 06-NOV-12 6919873050761 06-NOV-12
1    35739   6919873050761 06-NOV-12 6919873084996 06-NOV-12
1    35740   6919873084996 06-NOV-12 6919873122049 06-NOV-12
1    35741   6919873122049 06-NOV-12 6919873521767 06-NOV-12
1    35742   6919873521767 06-NOV-12 6919873952773 06-NOV-12
1    35743   6919873952773 06-NOV-12 6919874258549 06-NOV-12
1    35744   6919874258549 06-NOV-12 6919874472213 06-NOV-12
1    35745   6919874472213 06-NOV-12 6919874744856 06-NOV-12
1    35746   6919874744856 06-NOV-12 6919875113086 06-NOV-12
1    35747   6919875113086 06-NOV-12 6919875733337 06-NOV-12
1    35748   6919875733337 06-NOV-12 6919876139061 06-NOV-12
1    35749   6919876139061 06-NOV-12 6919876707162 06-NOV-12
1    35750   6919876707162 06-NOV-12 6919877706313 06-NOV-12
1    35751   6919877706313 06-NOV-12 6919877919039 06-NOV-12
1    35752   6919877919039 06-NOV-12 6919878024429 06-NOV-12
1    35753   6919878024429 06-NOV-12 6919878107673 06-NOV-12
1    35754   6919878107673 06-NOV-12 6919878258511 06-NOV-12
1    35755   6919878258511 06-NOV-12 6919878308336 06-NOV-12
1    35756   6919878308336 06-NOV-12 6919878424419 06-NOV-12
1    35757   6919878424419 06-NOV-12 6919878488485 06-NOV-12
1    35758   6919878488485 06-NOV-12 6919878827092 06-NOV-12
1    35759   6919878827092 06-NOV-12 6919879350098 07-NOV-12
1    35760   6919879350098 07-NOV-12 6919879675556 07-NOV-12
2    35949   6919870864360 06-NOV-12 6919871494640 06-NOV-12
2    35950   6919871494640 06-NOV-12 6919871887487 06-NOV-12
2    35951   6919871887487 06-NOV-12 6919872410655 06-NOV-12
2    35952   6919872410655 06-NOV-12 6919872552468 06-NOV-12
2    35953   6919872552468 06-NOV-12 6919872698940 06-NOV-12
2    35954   6919872698940 06-NOV-12 6919872872690 06-NOV-12
2    35955   6919872872690 06-NOV-12 6919872980371 06-NOV-12
2    35956   6919872980371 06-NOV-12 6919873085902 06-NOV-12
2    35957   6919873085902 06-NOV-12 6919873569082 06-NOV-12
2    35958   6919873569082 06-NOV-12 6919873949096 06-NOV-12
2    35959   6919873949096 06-NOV-12 6919874404640 06-NOV-12
2    35960   6919874404640 06-NOV-12 6919875011814 06-NOV-12
2    35961   6919875011814 06-NOV-12 6919875631429 06-NOV-12
2    35962   6919875631429 06-NOV-12 6919876324885 06-NOV-12
2    35963   6919876324885 06-NOV-12 6919876363526 06-NOV-12
2    35964   6919876363526 06-NOV-12 6919876748508 06-NOV-12
2    35965   6919876748508 06-NOV-12 6919877741784 06-NOV-12
2    35966   6919877741784 06-NOV-12 6919878108943 06-NOV-12
2    35967   6919878108943 06-NOV-12 6919878424477 06-NOV-12
2    35968   6919878424477 06-NOV-12 6919879012111 06-NOV-12
2    35969   6919879012111 06-NOV-12 6919879260589 07-NOV-12
2    35970   6919879260589 07-NOV-12 6919879350086 07-NOV-12
2    35971   6919879350086 07-NOV-12 6919879464935 07-NOV-12
2    35972   6919879464935 07-NOV-12 6919879548399 07-NOV-12
2    35973   6919879548399 07-NOV-12 6919879675564 07-NOV-12
RMAN> list incarnation;
List of Database Incarnations
DB Key Inc Key DB Name DB ID            STATUS Reset SCN Reset Time
1       1       ALEPHPR 3573460394       PARENT 1          13-MAY-10
2       2       ALEPHPR 3573460394       PARENT 2229467    28-JUN-10
3       3       ALEPHPR 3573460394       CURRENT 6918261828355 26-SEP-12The ASM structure is created...
ASMCMD> lsdg
State Type Rebal Sector Block AU Total_MB Free_MB Req_mir_free_MB Usable_file_MB Offline_disks Voting_files Name
MOUNTED EXTERN N 512 4096 1048576 509282 507421 0 507421 0 N DATA1/
MOUNTED EXTERN N 512 4096 1048576 50641 42850 0 42850 0 N FLASH/
ASMCMD> cd DATA1/ALEPHPR/DATAFILE
ASMCMD> pwd
+DATA1/ALEPHPR/DATAFILEBoth source and target databases are 11.2.0.2 PSU 6 running on Linux x64. I cannot use RMAN Duplicate since there is no visibility among different environments (PROD - QA in this case).
Any idea?
Thanks
Martin
Edited by: martin.morono on Nov 8, 2012 11:19 AM
Edited by: martin.morono on Nov 8, 2012 11:49 AM

Thanks Levi,
I slightly modified your script to recatalog the backup pieces since they are note stored at the same location in PR and QA.
No luck. The error message is different but the result is the same... it keeps failing.
RMAN> run {
2> allocate channel c1 device type disk;
3> allocate channel c2 device type disk;
4> restore controlfile from '/restorealeph/c-3573460394-20121107-01';
5> startup mount;
6> catalog start with '/restorealeph/';
7> restore database from tag 'BACKUP_ALEPHPR.TUR_110712030000';
8> }
allocated channel: c1
channel c1: SID=191 device type=DISK
allocated channel: c2
channel c2: SID=131 device type=DISK
Starting restore at 09 NOV 2012 13:11:09
channel c2: skipped, AUTOBACKUP already found
channel c1: restoring control file
channel c1: restore complete, elapsed time: 00:00:15
output file name=+DATA1/alephpr/controlfile/current.260.798747585
output file name=+FLASH/alephpr/controlfile/current.276.798747585
Finished restore at 09 NOV 2012 13:11:24
database is already started
database mounted
Starting implicit crosscheck backup at 09 NOV 2012 13:11:31
Crosschecked 52 objects
Finished implicit crosscheck backup at 09 NOV 2012 13:11:39
Starting implicit crosscheck copy at 09 NOV 2012 13:11:39
Crosschecked 2 objects
Finished implicit crosscheck copy at 09 NOV 2012 13:11:40
searching for all files in the recovery area
cataloging files...
cataloging done
List of Cataloged Files
=======================
File Name: +flash/ALEPHPR/ARCHIVELOG/2012_09_26/thread_2_seq_1.279.795017193
File Name: +flash/ALEPHPR/ARCHIVELOG/2012_09_26/thread_2_seq_34950.273.795014469
File Name: +flash/ALEPHPR/ARCHIVELOG/2012_09_26/thread_1_seq_1.281.795017413
File Name: +flash/ALEPHPR/ARCHIVELOG/2012_09_26/thread_1_seq_2.283.795017519
File Name: +flash/ALEPHPR/ARCHIVELOG/2012_09_26/thread_1_seq_3.290.795018411
File Name: +flash/ALEPHPR/ARCHIVELOG/2012_09_26/thread_1_seq_4.291.795018559
File Name: +flash/ALEPHPR/ARCHIVELOG/2012_09_26/thread_1_seq_5.292.795018707
File Name: +flash/ALEPHPR/ARCHIVELOG/2012_09_26/thread_1_seq_6.293.795018811
File Name: +flash/ALEPHPR/ARCHIVELOG/2012_09_26/thread_1_seq_7.294.795018899
File Name: +flash/ALEPHPR/ARCHIVELOG/2012_09_26/thread_1_seq_8.295.795020509
File Name: +flash/ALEPHPR/CONTROLFILE/Current.268.798725123
searching for all files that match the pattern /restorealeph/
List of Files Unknown to the Database
=====================================
File Name: /restorealeph/9cnpm51u_1_1
File Name: /restorealeph/9enpm6lj_1_1
File Name: /restorealeph/c-3573460394-20121107-00
File Name: /restorealeph/c-3573460394-20121107-01
File Name: /restorealeph/c-3573460394-20121106-01
Do you really want to catalog the above files (enter YES or NO)? YEs
cataloging files...
cataloging done
List of Cataloged Files
=======================
File Name: /restorealeph/9cnpm51u_1_1
File Name: /restorealeph/9enpm6lj_1_1
File Name: /restorealeph/c-3573460394-20121107-00
File Name: /restorealeph/c-3573460394-20121107-01
File Name: /restorealeph/c-3573460394-20121106-01
Starting restore at 09 NOV 2012 13:11:48
released channel: c1
released channel: c2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 11/09/2012 13:11:48
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 31 found to restore
RMAN-06023: no backup or copy of datafile 30 found to restore
RMAN-06023: no backup or copy of datafile 29 found to restore
RMAN-06023: no backup or copy of datafile 28 found to restore
RMAN-06023: no backup or copy of datafile 27 found to restore
RMAN-06023: no backup or copy of datafile 26 found to restore
RMAN-06023: no backup or copy of datafile 19 found to restore
RMAN-06023: no backup or copy of datafile 18 found to restore
RMAN-06023: no backup or copy of datafile 17 found to restore
RMAN-06023: no backup or copy of datafile 16 found to restore
RMAN-06023: no backup or copy of datafile 15 found to restore
RMAN-06023: no backup or copy of datafile 14 found to restore
RMAN-06023: no backup or copy of datafile 13 found to restore
RMAN-06023: no backup or copy of datafile 12 found to restore
RMAN-06023: no backup or copy of datafile 11 found to restore
RMAN-06023: no backup or copy of datafile 10 found to restore
RMAN-06023: no backup or copy of datafile 9 found to restore
RMAN-06023: no backup or copy of datafile 8 found to restore
RMAN-06023: no backup or copy of datafile 7 found to restore
RMAN-06023: no backup or copy of datafile 6 found to restore
RMAN-06023: no backup or copy of datafile 5 found to restore
RMAN-06023: no backup or copy of datafile 4 found to restore
RMAN-06023: no backup or copy of datafile 3 found to restore
RMAN-06023: no backup or copy of datafile 2 found to restore
RMAN-06023: no backup or copy of datafile 1 found to restore
RMAN>Just in case, I re-run this script including the crosscheck backup and the delete noprompt expired backups before restoring an the error messages were the same.
THanks again for your help.
Regards.
Martin
Edited by: martin.morono on Nov 9, 2012 7:21 AM

ORA-19007 when coping a table with an xml type in it to a new schema in the

ORA-19007 when coping a table with an xml type in it to a new schema in the same database.
Hi all,
When I copy a table with an xml type in it to a new schema in the same database I get an ora-19009.
The setup is as follows I have a schema a with table TABLE_WITH_XMLTYPE where data is:
CREATE
TABLE TABLE_WITH_XMLTYPE
FOLDER_ID NUMBER (10, 0) NOT NULL,
SEARCH_PROPERTIES XMLTYPE ,
CONSTRAINT TABLE_WITH_XMLTYPE PK PRIMARY KEY (FOLDERID) USING INDEX
XMLTYPE COLUMN SEARCH_PROPERTIES XMLSCHEMA
"http://xxxxxxx.net/FolderProperties.xsd" element "FolderProperties"
VARRAY SEARCH_PROPERTIES."XMLDATA"."PROPERTIES"."PROPERTY" STORE AS TABLE
PROPERTY_TABLE
(PRIMARY KEY (NESTED_TABLE_ID, ARRAY_INDEX)) ORGANIZATION INDEX OVERFLOW
Both schemas have the following xml schema registered as a local xml schema
BEGIN
DBMS_XMLSCHEMA.registerSchema(
SCHEMAURL => 'http://xxxxxxx.net/FolderProperties.xsd',
SCHEMADOC =>
'<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:xdb="http://xmlns.oracle.com/xdb"
xdb:storeVarrayAsTable="true">
<xs:element name="FolderProperties"
type="FolderPropertiesType"
xdb:defaultTable="FOLDER_SEARCH_PROPERTIES" />
<xs:complexType name="FolderPropertiesType" xdb:SQLType="FOLDERPROPERTIES_T">
<xs:sequence>
<xs:element name="FolderID" type="FolderIDType" minOccurs="1" xdb:SQLName="FOLDER_ID"/>
<xs:element name="Properties" type="PropertiesType" xdb:SQLName="PROPERTIES"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="PropertiesType" xdb:SQLType="PROPERTIES_T">
<xs:sequence>
<xs:element name="Property" type="PropertyType" maxOccurs="unbounded"
xdb:SQLName="PROPERTY" xdb:SQLCollType="PROPERTY_V"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="PropertyType" xdb:SQLType="PROPERTY_T">
<xs:sequence>
<xs:element name="DateValue" type="DateType" xdb:SQLName="DATE_VALUE"/>
<xs:element name="NumValue" type="NumType" xdb:SQLName="NUM_VALUE"/>
<xs:element name="StringValue" type="StringType" xdb:SQLName="STRING_VALUE"/>
</xs:sequence>
<xs:attribute name="Name" xdb:SQLName="NAME" xdb:SQLType="VARCHAR2">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:minLength value="1"/>
<xs:maxLength value="255"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:complexType>
<xs:simpleType name="FolderIDType">
<xs:restriction base="xs:integer"/>
</xs:simpleType>
<xs:simpleType name="DateType">
<xs:restriction base="xs:dateTime"/>
</xs:simpleType>
<xs:simpleType name="NumType">
<xs:restriction base="xs:decimal"/>
</xs:simpleType>
<xs:simpleType name="StringType">
<xs:restriction base="xs:string" />
</xs:simpleType>
</xs:schema>',
LOCAL => TRUE,
GENTYPES => TRUE,
GENTABLES => FALSE);
END;
when I try to do the following insert:
insert into schemaB.TABLE_WITH_XMLTYPE ( FOLDER_ID, SEARCH_PROPERTIES)
select FOLDER_ID, SEARCH_PROPERTIES from schemaB.TABLE_WITH_XMLTYPE;
I’ll get an ora-19007.
Can some one point me in the right direction how to solve this error.
Thanks Roelof.

Who did you create the second table, in other words, how did you COPY the table as you said...
If you created the second table via a CTAS (create table as select) then you will have created a table that is not the same as the original one. AFAIK I have once created an enhancement request for this after discovering that JDeveloper, for example, creates a "copy" via a CTAS which creates the wrong structure. Double check via package DBMS_METADATA.
SQL> set long 1000000
SQL> select DBMS_METADATA('TABLE','TABLE_WITH_XMLTYPE','SchemaA') from dual;
SQL> select DBMS_METADATA('TABLE','TABLE_WITH_XMLTYPE','SchemaB') from dual;If you have got two different tables, than Mark's solution should help.
M.
Edited by: Marco Gralike on Feb 15, 2009 11:16 AM

Getting ORA-06512/ORA-00972 ERROR WHILE EXECUTING THE PROCEDURE????

Hi ,
while executing this procedure , I am getting follwoing errors:
Create or Replace procedure ADD_CUSTOM_INDEX is
INDX_NOT_EXIST Number;
CREATE_SQL_STATMENT VARCHAR2(1500);
ALTER_SQL_STATMENT VARCHAR2(150);
CURSOR C1 IS select INDEX_NAME,CREATE_DDL FROM W_CUSTOM_TEST, WC_COMPANY_G WHERE W_CUSTOM_TEST.SYS_TENANT_ID = WC_COMPANY_G.BU_ID;
BEGIN
for V_ROW in C1 loop
     SELECT COUNT(USER_INDEXES.INDEX_NAME) INTO INDX_NOT_EXIST FROM USER_INDEXES WHERE USER_INDEXES.INDEX_NAME = V_ROW.index_name;
     IF INDX_NOT_EXIST = 0 THEN
     CREATE_SQL_STATMENT := ''|| '"'|| V_ROW.CREATE_DDL ||'"' ||'PARALLEL NOLOGGING';
     EXECUTE IMMEDIATE CREATE_SQL_STATMENT;
     ALTER_SQL_STATMENT := 'ALTER INDEX ' ||'"'|| V_ROW.INDEX_NAME ||'"'|| ' NOPARALLEL LOGGING';
     EXECUTE IMMEDIATE ALTER_SQL_STATMENT;
     END IF;
END LOOP;
END ADD_CUSTOM_INDEX;
ERROR at line 1:
ORA-00972: identifier is too long
ORA-06512: at "LOLAP.ADD_CUSTOM_INDEX", line 13
ORA-06512: at line 1.
sturtuce of W_custom_test table is as below:
CREATE TABLE "LOLAP"."W_CUSTOM_TEST"
("INDEX_NAME" VARCHAR2(30) NOT NULL ENABLE,
     "SYS_TENANT_ID" VARCHAR2(15) NOT NULL ENABLE,
"CREATE_DDL" VARCHAR2(1200),
"COMMENTS" VARCHAR2(200),
     "STAT_CD" VARCHAR2(30) DEFAULT 'Active' NOT NULL ENABLE,
     "CREATED" DATE DEFAULT SYSDATE NOT NULL ENABLE,
     "LAST_UPD" DATE DEFAULT SYSDATE NOT NULL ENABLE
Any Pointer??????

Hi
Instead of giving as below, go for the not null constraints.
"STAT_CD" VARCHAR2(30) DEFAULT 'Active' NOT NULL ENABLE,
"CREATED" DATE DEFAULT SYSDATE NOT NULL ENABLE,
"LAST_UPD" DATE DEFAULT SYSDATE NOT NULL ENABLE
That should help
Regards
Sudheer

ORA-00972: identifier is too long

Hi All,
I get the error ORA-00972: identifier is too long during installation of NW2004s SR2 Java system with DI. This error is seen on the step Perform post load activites. i have made the changes as suggested by SAP note: 314671. But the error still persists. Can anyone suggest what further more should be done here?
Oracle is unable to delete : OPS$<14 letter host name>\SAPSERVICESR3 and hence the error.
the output from ora_sql_results.log
=============================================================
2008-04-28, 19:04:56 SAPINST ORACLE start logging for
@@SAPDBA_ADDITIONAL.SQL
exit;
Output of SQL executing program:
SQL*Plus: Release 10.2.0.1.0 - Production on Mon Apr 28 19:04:56 2008
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
Connected.
old   3:   :sSchemaUser := upper('&&1');
new   3:   :sSchemaUser := upper('SAPSR3DB');
old 19:   if upper('&&2') = 'NT' then
new 19:   if upper('NT') = 'NT' then
old 21:     :sDomain := upper('&&3');
new 21:     :sDomain := upper('[14 letter Host Name]\SIDadm');
old 32:   elsif upper('&&2') = 'UNIX' then
new 32:   elsif upper('NT') = 'UNIX' then
old 37:     RAISE_APPLICATION_ERROR(-20004,'Invalid OS, must be "NT" or "UNIX": ' || upper('&&2'));
new 37:     RAISE_APPLICATION_ERROR(-20004,'Invalid OS, must be "NT" or "UNIX": ' || upper('NT'));
using following Parameters:
. Schema User:                  SAPSR3DB
. Parametervalue os_authent_prefix:   OPS$
. OPS$SIDADM:                      OPS$[14 letter Host Name]\SIDADM
. SAP SID:                      SR3
. DB SID:                      SID
. R/3 Service User:                 OPS$[14 letter Host Name]\SAPSERVICESR3
. Computer or Domain:                 [14 letter Host Name]\SIDADM
old 119:   if upper('&&4') = 'SYN' then
new 119:   if upper('SYN') = 'SYN' then
old 137:   if upper('&&4') = 'SYN' then
new 137:   if upper('SYN') = 'SYN' then
create synonym: SAP_SDBAH SAPSR3DB.SDBAH
create synonym: SAP_SDBAH SAPSR3DB.SDBAD
unable to delete user: OPS$[14 letter Host Name]\SAPSERVICESR3
begin
ERROR at line 1:
ORA-00972: identifier is too long
ORA-06512: at line 46
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
SAPINST: End of output of SQL executing program C:\oracle\product\10.2.0\db_1/bin/sqlplus.
SAPINST found errors.
SAPINST The current process environment may be found in sapinst_ora_environment.log.
2008-04-28, 19:04:56 SAPINST ORACLE stop logging
Thanks in advance,
Arun E V

Hi Markus/Stefan,
Thanks for the quick answer. I know i am using a unsupported version, but that should not be a problem here. Though i have not run the installer from the script, still the DB is a successful installation and i have used it like this a few times.
Stefan, I have seen the note and made the required modification but still the issue persists. Is there anything more that i need to do apart from what is mentioned in the note?
The trouble is we are not in a position to change the host name as suggested and would prefer to continue with the same name.
Thanks,
Arun E V

ORA-00972 - when autoextending a datafile

Similar Messages

Maybe you are looking for