11.1 to 11.2 upgrade - ORA-25319 errors

I recently upgraded from 11.1 to 11.2. The upgrade seemed to work with no errors.
Since the upgrade I have been getting LOTS and LOTS of ORA-25319.
I cannot find any details on what might be causing this or how to fix it.
I have raised an SR and I have search the support DB for this error, but not resolutations can be found.
Has anyone come across this error ?
Thanks
Brendan
PS. While writing this post I've had 3 emails reporting this error

In my case, starting the OEM agent produces the error. And the agent eventually has be be stopped, because it takes all available CPU. But, also every now and then MMON produces them . I have just sent the errorstack trace to oracle. Usually only get one response a day. I have tried to escalate, the only option is a "prod system down" status at this point I assume.
I have compiled invalid objects numerous times, no system objects (other than a couple obsolete ones) are invalid.
Thu Jun 16 09:55:17 2011
Errors in file /orasys/diag/rdbms/stlpeve/stlpeve/trace/stlpeve_mmon_3879030.trc (incident=48223):
ORA-25319: Queue table repartitioning aborted
Incident details in: /orasys/diag/rdbms/stlpeve/stlpeve/incident/incdir_48223/stlpeve_mmon_3879030_i48223.trc
==
Dump file /orasys/diag/rdbms/stlpeve/stlpeve/incident/incdir_48223/stlpeve_mmon_3879030_i48223.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
ORACLE_HOME = /orasys/ora11202
System name: AIX
Node name: stlpora40
Release: 1
Version: 6
Machine: 00F609144C00
Instance name: stlpeve
Redo thread mounted by this instance: 1
Oracle process number: 16
Unix process pid: 3879030, image: oracle@stlpora40 (MMON)
*** 2011-06-16 09:55:17.095
*** SESSION ID:(1217.1) 2011-06-16 09:55:17.095
*** CLIENT ID:() 2011-06-16 09:55:17.095
*** CLIENT ID:() 2011-06-16 09:55:17.095
*** SERVICE NAME:(SYS$BACKGROUND) 2011-06-16 09:55:17.095
*** MODULE NAME:() 2011-06-16 09:55:17.095
*** ACTION NAME:() 2011-06-16 09:55:17.095
Dump continued from file: /orasys/diag/rdbms/stlpeve/stlpeve/trace/stlpeve_mmon_3879030.trc
ORA-25319: Queue table repartitioning aborted
========= Dump for incident 48223 (ORA 25319) ========
*** 2011-06-16 09:55:17.098
dbkedDefDump(): Starting incident default dumps (flags=0x2, level=3, mask=0x0)
----- SQL Statement (None) -----
Current SQL information unavailable - no cursor.
----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)

Similar Messages

Startup upgrade ORA-00205: error in identifying control file

Hi,
I am doing a manual upgrade from 10.2.04 to 11.2.03.
I have installed 11.2.0.3.
Ran utlu112i.sql
Copied TNSNAMES and LISTENER.ora,init.ora from 10g home to 11g home respective directories.
Commented all dump_dest paramteres in 11g init.ora and added diagnostic_dest parameter
exported all the varaiables as follows.
export ORACLE_HOME=/oracle/ora11203
export PATH=$ORACLE_HOME/bin:$PATH
export ORACLE_SID=OMIGTEST
export TNS_ADMIN=$ORACLE_HOME/network/admin
export ORACLE_BASE=/oracle/ora11203/app/ora11203
Now when i try to start DB from the unix session where all of above variables are set,i am getting following issue.
SQL> startup upgrade
ORACLE instance started.
Total System Global Area 1636892672 bytes
Fixed Size                  2183056 bytes
Variable Size            1090519152 bytes
Database Buffers          536870912 bytes
Redo Buffers                7319552 bytes
ORA-00205: error in identifying control file, check alert log for more info
Alert log says as below.
ORACLE_BASE from environment = /oracle/ora11203/app/ora11203
Thu Aug 23 15:03:36 2012
ALTER DATABASE   MOUNT
ORA-00210: cannot open the specified control file
ORA-00202: control file: '/oracle/ora11203/dbs/cntrlOMIGTEST.dbf'
ORA-27037: unable to obtain file status
HPUX-ia64 Error: 2: No such file or directory
Additional information: 3
ORA-205 signalled during: ALTER DATABASE   MOUNT...In init.ora of 11g (which is copied from 10g) ,i have commented our control file path entry.
Kindly assist me as i am doing upgrade for the first time.
Thanks
Edited by: user10698496 on Aug 24, 2012 2:47 AM

Hi,
Issue of sqlplus is solved after setting proper LD_LIBRARY_PATH.
But eve after that startup upgrade showing same error.
sqlplus '/as sysdba'
SQL*Plus: Release 11.2.0.3.0 Production on Thu Aug 23 16:22:16 2012
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing optionsSQL> startup upgrade
ORACLE instance started.
Total System Global Area 1636892672 bytes
Fixed Size 2183056 bytes
Variable Size 1090519152 bytes
Database Buffers 536870912 bytes
Redo Buffers 7319552 bytes
ORA-00205: error in identifying control file, check alert log for more info
Do i copy control file from 10g home and place in in 11g path and mention it in init.ora before upgrade?
Thanks

9.0.4 to 10.1.2 upgrade ora-00600 error

We are upgrading our forms from 9.0.4 to 10.1.2... We are having some issues converting a couple of forms. Most forms are converting just fine and work great. One of the forms has this error in a when-button-pressed trigger...
ora-00600: internal error code, arguments: [KGHALO2], [0x0], [], [], [], [], [], []I commented out some code in the trigger untill the error went away. Form Builder is having an issue with a database plsql package.procedure call that is actually a wrapper to a java class stored in the database. The code in this 10.1.2 form is identical to the code in the 9.0.4 form. The 9.0.4 form works fine and calls this wrapper A-ok. The 10.1.2 form throws the error above. This error hapens when compiling the when-button-pressed code in form builder on my local pc and when trying to compile the form on the app server. Am I missing a java setting somewhere in both places?
create or replace
PACKAGE        sims_marrs_report IS
PROCEDURE insert_clob_data(dot_case_num    in varchar2,
                             docxml_id       in number,
                             temp_report_pk in number,
                             marrs_report_pk in number,
                             out_error       out varchar2)
as language java name
     'AccidentReport.create(java.lang.String,
                            oracle.sql.NUMBER,
                            oracle.sql.NUMBER,
                            oracle.sql.NUMBER,
                            java.lang.String[])';
end;Edited by: Mark Reichman on Oct 16, 2008 2:46 PM

You are a genius.. :) So, if you want to call java in the database from forms 10.1.2 you have to double wrap your java...
According to metalink Note:368022.1 creating another wrapper around the plsql wrapper will fix the issue.

ORA-12709: error while loading create database character set after upgrade

Dear All
i m getting ORA-12709: error while loading create database character set, After upgraded the database from 10.2.0.3 to 11.2.0.3 in ebusiness suit env.
current application version 12.0.6
please help me to resolve it.
SQL> startup;
ORACLE instance started.
Total System Global Area 1.2831E+10 bytes
Fixed Size 2171296 bytes
Variable Size 2650807904 bytes
Database Buffers 1.0133E+10 bytes
Redo Buffers 44785664 bytes
ORA-12709: error while loading create database character set
-bash-3.00$ echo $ORA_NLS10
/u01/oracle/PROD/db/teche_st/11.2.0/nls/data/9idata
export ORACLE_BASE=/u01/oracle
export ORACLE_HOME=/u01/oracle/PROD/db/tech_st/11.2.0
export PATH=$ORACLE_HOME/bin:$ORACLE_HOME/perl/bin:$PATH
export PERL5LIB=$ORACLE_HOME/perl/lib/5.10.0:$ORACLE_HOME/perl/site_perl/5.10.0
export ORA_NLS10=/u01/oracle/PROD/db/teche_st/11.2.0/nls/data/9idata
export ORACLE_SID=PROD
-bash-3.00$ pwd
/u01/oracle/PROD/db/tech_st/11.2.0/nls/data/9idata
-bash-3.00$ ls -lh |more
total 56912
-rw-r--r-- 1 oracle oinstall 951 Jan 15 16:05 lx00001.nlb
-rw-r--r-- 1 oracle oinstall 957 Jan 15 16:05 lx00002.nlb
-rw-r--r-- 1 oracle oinstall 959 Jan 15 16:05 lx00003.nlb
-rw-r--r-- 1 oracle oinstall 984 Jan 15 16:05 lx00004.nlb
-rw-r--r-- 1 oracle oinstall 968 Jan 15 16:05 lx00005.nlb
-rw-r--r-- 1 oracle oinstall 962 Jan 15 16:05 lx00006.nlb
-rw-r--r-- 1 oracle oinstall 960 Jan 15 16:05 lx00007.nlb
-rw-r--r-- 1 oracle oinstall 950 Jan 15 16:05 lx00008.nlb
-rw-r--r-- 1 oracle oinstall 940 Jan 15 16:05 lx00009.nlb
-rw-r--r-- 1 oracle oinstall 939 Jan 15 16:05 lx0000a.nlb
-rw-r--r-- 1 oracle oinstall 1006 Jan 15 16:05 lx0000b.nlb
-rw-r--r-- 1 oracle oinstall 1008 Jan 15 16:05 lx0000c.nlb
-rw-r--r-- 1 oracle oinstall 998 Jan 15 16:05 lx0000d.nlb
-rw-r--r-- 1 oracle oinstall 1005 Jan 15 16:05 lx0000e.nlb
-rw-r--r-- 1 oracle oinstall 926 Jan 15 16:05 lx0000f.nlb
-rw-r--r-- 1 oracle oinstall 1.0K Jan 15 16:05 lx00010.nlb
-rw-r--r-- 1 oracle oinstall 958 Jan 15 16:05 lx00011.nlb
-rw-r--r-- 1 oracle oinstall 956 Jan 15 16:05 lx00012.nlb
-rw-r--r-- 1 oracle oinstall 1005 Jan 15 16:05 lx00013.nlb
-rw-r--r-- 1 oracle oinstall 970 Jan 15 16:05 lx00014.nlb
-rw-r--r-- 1 oracle oinstall 950 Jan 15 16:05 lx00015.nlb
-rw-r--r-- 1 oracle oinstall 1.0K Jan 15 16:05 lx00016.nlb
-rw-r--r-- 1 oracle oinstall 957 Jan 15 16:05 lx00017.nlb
-rw-r--r-- 1 oracle oinstall 932 Jan 15 16:05 lx00018.nlb
-rw-r--r-- 1 oracle oinstall 932 Jan 15 16:05 lx00019.nlb
-rw-r--r-- 1 oracle oinstall 951 Jan 15 16:05 lx0001a.nlb
-rw-r--r-- 1 oracle oinstall 944 Jan 15 16:05 lx0001b.nlb
-rw-r--r-- 1 oracle oinstall 953 Jan 15 16:05 lx0001c.nlb
Starting up:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options.
ORACLE_HOME = /u01/oracle/PROD/db/tech_st/11.2.0
System name: SunOS
Node name: proddb3.zakathouse.org
Release: 5.10
Version: Generic_147440-19
Machine: sun4u
Using parameter settings in server-side spfile /u01/oracle/PROD/db/tech_st/11.2.0/dbs/spfilePROD.ora
System parameters with non-default values:
processes = 200
sessions = 400
timed_statistics = TRUE
event = ""
shared_pool_size = 416M
shared_pool_reserved_size= 40M
nls_language = "american"
nls_territory = "america"
nls_sort = "binary"
nls_date_format = "DD-MON-RR"
nls_numeric_characters = ".,"
nls_comp = "binary"
nls_length_semantics = "BYTE"
memory_target = 11G
memory_max_target = 12G
control_files = "/u01/oracle/PROD/db/apps_st/data/cntrl01.dbf"
control_files = "/u01/oracle/PROD/db/tech_st/10.2.0/dbs/cntrl02.dbf"
control_files = "/u01/oracle/PROD/db/apps_st/data/cntrl03.dbf"
db_block_checksum = "TRUE"
db_block_size = 8192
compatible = "11.2.0.0.0"
log_archive_dest_1 = "LOCATION=/u01/oracle/PROD/db/apps_st/data/archive"
log_archive_format = "%t_%s_%r.dbf"
log_buffer = 14278656
log_checkpoint_interval = 100000
log_checkpoint_timeout = 1200
db_files = 512
db_file_multiblock_read_count= 8
db_recovery_file_dest = "/u01/oracle/fast_recovery_area"
db_recovery_file_dest_size= 14726M
log_checkpoints_to_alert = TRUE
dml_locks = 10000
undo_management = "AUTO"
undo_tablespace = "APPS_UNDOTS1"
db_block_checking = "FALSE"
session_cached_cursors = 500
utl_file_dir = "/usr/tmp"
utl_file_dir = "/usr/tmp"
utl_file_dir = "/u01/oracle/PROD/db/tech_st/10.2.0/appsutil/outbound"
utl_file_dir = "/u01/oracle/PROD/db/tech_st/10.2.0/appsutil/outbound/PROD_proddb3"
utl_file_dir = "/usr/tmp"
plsql_code_type = "INTERPRETED"
plsql_optimize_level = 2
job_queue_processes = 2
cursor_sharing = "EXACT"
parallel_min_servers = 0
parallel_max_servers = 8
core_dump_dest = "/u01/oracle/PROD/db/tech_st/10.2.0/admin/PROD_proddb3/cdump"
audit_file_dest = "/u01/oracle/admin/PROD/adump"
db_name = "PROD"
open_cursors = 600
pga_aggregate_target = 1G
workarea_size_policy = "AUTO"
optimizer_secure_view_merging= FALSE
aq_tm_processes = 1
olap_page_pool_size = 4M
diagnostic_dest = "/u01/oracle"
max_dump_file_size = "20480"
Tue Jan 15 16:16:02 2013
PMON started with pid=2, OS id=18608
Tue Jan 15 16:16:02 2013
PSP0 started with pid=3, OS id=18610
Tue Jan 15 16:16:03 2013
VKTM started with pid=4, OS id=18612 at elevated priority
VKTM running at (10)millisec precision with DBRM quantum (100)ms
Tue Jan 15 16:16:03 2013
GEN0 started with pid=5, OS id=18616
Tue Jan 15 16:16:03 2013
DIAG started with pid=6, OS id=18618
Tue Jan 15 16:16:03 2013
DBRM started with pid=7, OS id=18620
Tue Jan 15 16:16:03 2013
DIA0 started with pid=8, OS id=18622
Tue Jan 15 16:16:03 2013
MMAN started with pid=9, OS id=18624
Tue Jan 15 16:16:03 2013
DBW0 started with pid=10, OS id=18626
Tue Jan 15 16:16:03 2013
LGWR started with pid=11, OS id=18628
Tue Jan 15 16:16:03 2013
CKPT started with pid=12, OS id=18630
Tue Jan 15 16:16:03 2013
SMON started with pid=13, OS id=18632
Tue Jan 15 16:16:04 2013
RECO started with pid=14, OS id=18634
Tue Jan 15 16:16:04 2013
MMON started with pid=15, OS id=18636
Tue Jan 15 16:16:04 2013
MMNL started with pid=16, OS id=18638
DISM started, OS id=18640
ORACLE_BASE from environment = /u01/oracle
Tue Jan 15 16:16:08 2013
ALTER DATABASE MOUNT
ORA-12709 signalled during: ALTER DATABASE MOUNT...

ORA-12709 signalled during: ALTER DATABASE MOUNT...Do you have any trace files generated at the time you get this error?
Please see these docs.
ORA-12709: WHILE STARTING THE DATABASE [ID 1076156.6]
Upgrading from 9i to 10gR2 Fails With ORA-12709 : Error While Loading Create Database Character Set [ID 732861.1]
Ora-12709 While Trying To Start The Database [ID 311035.1]
ORA-12709 when Mounting the Database [ID 160478.1]
How to Move From One Database Character Set to Another at the Database Level [ID 1059300.6]
Thanks,
Hussein

10.2 to 11.2 upgrade ORA-20011/ORA-12702

ORA-20011/ORA-12702 error received post upgrade (in 11g) when running full database stats,
stats worked in 10g. upgrade appeared successful, no errors.
database:
freshly upgraded from 10.2.0.3.0 =>
Oracle Database 11g Release 11.2.0.1.0 - 64bit Production
PL/SQL Release 11.2.0.1.0 - Production
CORE 11.2.0.1.0 Production
TNS for Solaris: Version 11.2.0.1.0 - Production
NLSRTL Version 11.2.0.1.0 - Production
server:
SunOS xxxxxx 5.10 Generic_Virtual sun4v sparc sun4v
64-bit sparcv9 kernel modules
SQL> exec dbms_stats.gather_database_stats;
BEGIN dbms_stats.gather_database_stats; END;
ERROR at line 1:
ORA-20011: Approximate NDV failed: ORA-12702: invalid NLS parameter string used in SQL function
ORA-06512: at "SYS.DBMS_STATS", line 20508
ORA-06512: at "SYS.DBMS_STATS", line 20993
ORA-06512: at "SYS.DBMS_STATS", line 21150
ORA-06512: at "SYS.DBMS_STATS", line 21109
ORA-06512: at line 1
SQL> exec dbms_stats.gather_database_stats_job_proc;
PL/SQL procedure successfully completed.
SQL> exec DBMS_STATS.GATHER_DATABASE_STATS (estimate_percent =>100, block_sample=>FALSE, method_opt=>'for all columns size auto', degree=>null, cascade=>true, no_invalidate=>false, options=>'GATHER STALE', gather_sys=>FALSE);
PL/SQL procedure successfully completed.
SQL> !env | grep NLS
NLS_LANG=american
NLS_DATE_FORMAT=YYYY/MM/DD HH24:MI:SS
SQL> select userenv('LANGUAGE') from dual;
USERENV('LANGUAGE')
AMERICAN_AMERICA.AL32UTF8
SQL> select * from v$nls_parameters where parameter like '%CHARACTERSET%';
PARAMETER
VALUE
NLS_CHARACTERSET
AL32UTF8
NLS_NCHAR_CHARACTERSET
AL16UTF16
any ideas, please? I haven't seen this elsewhere..

may be its due to version issue. you Source database is 10.2.0.3.0 and it should be 10.2.0.4.0
Prerequisite
1. your source database must be atleast 10.2.0.4.0 or Patch set for 10.2.0.2.5 should be installed
2. Time version must be >= 4
Regards
Sanchit Gupta

JAEHYLEE (R12 FND) R12 Upgrade후에 ORA-20001 FND_CANT_INSERT_USER_ROLE

Purpose
R12 Upgrade후에 System admin에서 권한을 assign할려고 할때
GET ORA-20001 FND_CANT_INSERT_USER_ROLE 에러가 자주 발생 합니다.
Cause
Upgrade to 12.0.2.
ORA-20001 error는 이미 권한이 할당되어 있을때 발생합니다.
The ORA-20001 error is often caused by the responsibility already being assigned.
Solution
아래 "Workflow Directory Services User/Role Validation"을
parameters : 100000, Yes, Yes, No로 수행을 하시기 바랍니다.
Reference
Note 454988.1

please check note( Supplier Registration Page Gets Error java.sql.SQLException: ORA-20001 )
Note:330350.1 althogh its for 11i but the cuz seems right
Cause
The root cause is that FND.H changes fnd_user_resp_groups from a table to a view which return
end_date as year 9999 instead of the value of null in the underlying data. The code in
confirm_has_resp expects the end_date of the pos guest user resp to user guest to be null, and if
not, trying to insert the assignment and fail (because the assignment already exists and active).
Development provide the cause in bug 3610633
fadi

ORA-01092 error while upgrading database from 9.2.0.6 to 10.2.0.1

Hi ,
Am getting ORA-01092 error while upgrading database to 10.2.0.1 from 9.2.0.6
I executed the catupgrd.sql successfully and recompiled invaild objects.
After that i tried to startup the database,but am getting the error:
sql>startup
oracle instance started
database mounted
ORA-01092 : Oracle instance terminated. Disconnection forced
I checked alert log file.
I am getting the following errors
Errors in file /u01/......./udump/VIS_ora/7179.trc
ORA-00604: error occurred at recursive SQL level 1
ORA-00607: internal error occurred while making change to a datablock
ORA-00600: internal error code, arguments [4194],[70] ,[39] [ ] []
Error 604 happened during database open . Shutting down database
instance terminated by USER pid =7179
ORA-01092 error Signaled during alter database open
Is there any block corruption? could u please share the solution for these errors?

Hi;
You are hitting ORA-00600: error which mean you may need to work oracle support for your issue.Pelase check below note if its not help i suggest rise sr
Troubleshoot an ORA-600 or ORA-7445 Error Using the Error Lookup Tool [ID 153788.1]
Regard
Helios

Ora-00604:error occurred at recursive SQL level 1 and Ora-04023

hi all
i am using oracle linux 5.5 and oracle Database 11g R2 while shutingdown the database i am getting
the following errors.
SQL> shutdown immediate;
Ora-00604:error occurred at recursive SQL level 1
Ora-04023: object select count(*) from reg$SQL>plz can anyone help me out?

Couple of questions related to this issue:
1.Is there anything in alert log. Post last 50 lines from alert log.
2.Is there any trace / log generated by Oracle ?
3.What is Memory_Target parameter value ?
4.What is value of statistics_level parameter ?
5.Did you perform any failed upgradation ?
6.Are there any invalid objects in database ?
Generally ORA-00604 is related to insufficient size of shared pool. Now, i am googling how to get a proper value of shared pool size ? I got that there is a view v$shared_pool_advice which will tell me the answer of this question. Ok, it means now question is how do i get the proper value of shared pool from v$shared_pool_advice; i mean how do i interpret this v$shared_pool_advice view ?
No problem docs are there to answer this question : (How i got this link ? Open a new page---http://tahiti.oracle.com---selected 11.2 docs--in the left hand sided there is a search text box i entered v$shared_pool_advice and i got couple of links)
http://download.oracle.com/docs/cd/E11882_01/server.112/e17110/dynviews_3037.htm#REFRN30239
I will read these links and now i will query this and DBA_HIST_SHARED_POOL_ADVICE views, interpret the values. Ok, but what about my original question i.e. ORA-00604 and 4023 ? If i am at this stage, understood all the values, it means now i can understand the meaning / sense of resizing of shared pool.
ALTER SYSTEM SET statistics_level=TYPICAL SCOPE=SPFILE;
You can monitor V$SGA_RESIZE_OPS to identify the range of values that Oracle is automatically resizing the DB_CACHE_SIZE and SHARED_POOL_SIZE components to. Then, pick an appropriate minimum value based on the range. There's no "magic formula". But V$SGA_RESIZE_OPS shows the sizes that Oracle has been automatically been resizing the SGA components to. The Buffer Cache Advisory section of the AWR report or V$DB_CACHE_ADVICE, V$SHARED_POOL_ADVICE, V$SGA_TARGET_ADVICE and DBA_HIST_SGA_TARGET_ADVICE are views that provide advisory information as well. Hemant @ SGA_MAX_SIZE and SGA_TARGET how to set minimum for pools
So, these are the baby steps if i ever gets ORA-00604 and ORA-04023 on my test database. Do all these and feel free to post the next doubt, i am sure you will get the correct answer.
Regards
Girish Sharma

Ora-00604 error while runing script

Hi Guys..
Let me describe the environment
My OS is windows 2008 R2 server 64-bit.. Database version is Oracle 11gR2
I recently upgraded the oracle DB from 11gr1 to 11gr2 .It upgraded successfully without any errors and the updated DB on 11gr2 is working fine..
Now one of the employee is getting below errror while executing a script which calles a plsql package.
ORA-00604: error occurred at recursive SQL level 1
ORA-00001: unique constraint (SYS.I_PLSCOPE_SIG_IDENTIFIER$) violated
I googled around and found that its related to plscope_settings parameter..
select name,value from v$parameter where name = 'plscope_settings';
the output was IDENTIFIERS:NONE
Further investigations revealed that my DB is running with the (default) init-parameter “plscope_settings=IDENTIFIERS:NONE”, while my SQL-Developer (v3.0) started every session with the default-setting “plscope_settings=IDENTIFIERS:ALL” (see menu EXTRAS>PREFERENCES>DATABASE>PL/SQL-COMPILER).
so i changed the settings to NONE in Sql Developer too..then recompiled the package but the error is still there when i execute the same package..
Its high time..i need to resolve it over the weekend..so can u plz share ur valuable comments..
Let me if u want any info from my end so that u get more clearer about the prob...

sai121 wrote:
Hi Guys..
Let me describe the environment
My OS is windows 2008 R2 server 64-bit.. Database version is Oracle 11gR2
I recently upgraded the oracle DB from 11gr1 to 11gr2 .It upgraded successfully without any errors and the updated DB on 11gr2 is working fine..
Now one of the employee is getting below errror while executing a script which calles a plsql package.
ORA-00604: error occurred at recursive SQL level 1
ORA-00001: unique constraint (SYS.I_PLSCOPE_SIG_IDENTIFIER$) violated
I googled around and found that its related to plscope_settings parameter..
select name,value from v$parameter where name = 'plscope_settings';
the output was IDENTIFIERS:NONE
Further investigations revealed that my DB is running with the (default) init-parameter “plscope_settings=IDENTIFIERS:NONE”, while my SQL-Developer (v3.0) started every session with the default-setting “plscope_settings=IDENTIFIERS:ALL” (see menu EXTRAS>PREFERENCES>DATABASE>PL/SQL-COMPILER).
so i changed the settings to NONE in Sql Developer too..then recompiled the package but the error is still there when i execute the same package..
Its high time..i need to resolve it over the weekend..so can u plz share ur valuable comments..
Let me if u want any info from my end so that u get more clearer about the prob...
bcm@bcm-laptop:~$ oerr ora 1
00001, 00000, "unique constraint (%s.%s) violated"
// *Cause: An UPDATE or INSERT statement attempted to insert a duplicate key.
// For Trusted Oracle configured in DBMS MAC mode, you may see
// this message if a duplicate entry exists at a different level.
// *Action: Either remove the unique restriction or do not insert the key.

Re: BUG? APEX 4.0: ORA-20503 error editing report with 400+ columns

Hello Everyone.
I've run into something quite strange and am hoping you can help me.
I am using Apex 4.0.1 and Oracle version 10.2.0.5. I've created a "classical" report in which the underlying SQL is a very simple:
select * from pvtabThe Oracle table pvtab consists of 419 columns, all of which are varchar2(88) and number type. That's it.
When I run the report, al of the columns show up as expected.
However, when I go into the "Report Attributes" tab and click on one of the fields (any of them, it doesn't matter which one), I immediately get the following error:
ORA-20503: Current version of data in database has changed since user initiated update process. current checksum = "598CAA7B68746A66F4B99E1512C36DED" application checksum = "0"If if replace the "*" with a few actual column names, then I am able to access any of these columns without problem.
If I put back the "*", I then encounter this error again.
I have never seen this error with other SQL SELECT statements in which I use the "*" qualifier to retrieve all columns from the table.
And so, I am wondering if the error is caused because of the large number of columns (419) in my table.
I've seen this same error mentioned in connection with forms but never with a report.
So, is there some limit to the number of columns one can have in a "classic" or interactive report?
Any idea why I would be getting this error?
Here is the DDL for my table pvtab:
CREATE TABLE "PVTAB"
   (     "MICRO" VARCHAR2(4),
     "PRIM" VARCHAR2(4),
     "UNIT" NUMBER,
     "SEC_REF_1" NUMBER,
     "SECN_1" VARCHAR2(88),
     "SEC_REF_2" NUMBER,
     "SECN_2" VARCHAR2(88),
     "SEC_REF_3" NUMBER,
     "SECN_3" VARCHAR2(88),
     "SEC_REF_4" NUMBER,
     "SECN_4" VARCHAR2(88),
     "SEC_REF_5" NUMBER,
     "SECN_5" VARCHAR2(88),
     "SEC_REF_6" NUMBER,
     "SECN_6" VARCHAR2(88),
     "SEC_REF_7" NUMBER,
     "SECN_7" VARCHAR2(88),
     "SEC_REF_8" NUMBER,
     "SECN_8" VARCHAR2(88),
     "SEC_REF_9" NUMBER,
     "SECN_9" VARCHAR2(88),
     "SEC_REF_10" NUMBER,
     "SECN_10" VARCHAR2(88),
     "SEC_REF_11" NUMBER,
     "SECN_11" VARCHAR2(88),
     "SEC_REF_12" NUMBER,
     "SECN_12" VARCHAR2(88),
     "SEC_REF_13" NUMBER,
     "SECN_13" VARCHAR2(88),
     "SEC_REF_14" NUMBER,
     "SECN_14" VARCHAR2(88),
     "SEC_REF_15" NUMBER,
     "SECN_15" VARCHAR2(88),
     "SEC_REF_16" NUMBER,
     "SECN_16" VARCHAR2(88),
     "SEC_REF_17" NUMBER,
     "SECN_17" VARCHAR2(88),
     "SEC_REF_18" NUMBER,
     "SECN_18" VARCHAR2(88),
     "SEC_REF_19" NUMBER,
     "SECN_19" VARCHAR2(88),
     "SEC_REF_20" NUMBER,
     "SECN_20" VARCHAR2(88),
     "SEC_REF_21" NUMBER,
     "SECN_21" VARCHAR2(88),
     "SEC_REF_22" NUMBER,
     "SECN_22" VARCHAR2(88),
     "SEC_REF_23" NUMBER,
     "SECN_23" VARCHAR2(88),
     "SEC_REF_24" NUMBER,
     "SECN_24" VARCHAR2(88),
     "SEC_REF_25" NUMBER,
     "SECN_25" VARCHAR2(88),
     "SEC_REF_26" NUMBER,
     "SECN_26" VARCHAR2(88),
     "SEC_REF_27" NUMBER,
     "SECN_27" VARCHAR2(88),
     "SEC_REF_28" NUMBER,
     "SECN_28" VARCHAR2(88),
     "SEC_REF_29" NUMBER,
     "SECN_29" VARCHAR2(88),
     "SEC_REF_30" NUMBER,
     "SECN_30" VARCHAR2(88),
     "SEC_REF_31" NUMBER,
     "SECN_31" VARCHAR2(88),
     "SEC_REF_32" NUMBER,
     "SECN_32" VARCHAR2(88),
     "SEC_REF_33" NUMBER,
     "SECN_33" VARCHAR2(88),
     "SEC_REF_34" NUMBER,
     "SECN_34" VARCHAR2(88),
     "SEC_REF_35" NUMBER,
     "SECN_35" VARCHAR2(88),
     "SEC_REF_36" NUMBER,
     "SECN_36" VARCHAR2(88),
     "SEC_REF_37" NUMBER,
     "SECN_37" VARCHAR2(88),
     "SEC_REF_38" NUMBER,
     "SECN_38" VARCHAR2(88),
     "SEC_REF_39" NUMBER,
     "SECN_39" VARCHAR2(88),
     "SEC_REF_40" NUMBER,
     "SECN_40" VARCHAR2(88),
     "SEC_REF_41" NUMBER,
     "SECN_41" VARCHAR2(88),
     "SEC_REF_42" NUMBER,
     "SECN_42" VARCHAR2(88),
     "SEC_REF_43" NUMBER,
     "SECN_43" VARCHAR2(88),
     "SEC_REF_44" NUMBER,
     "SECN_44" VARCHAR2(88),
     "SEC_REF_45" NUMBER,
     "SECN_45" VARCHAR2(88),
     "SEC_REF_46" NUMBER,
     "SECN_46" VARCHAR2(88),
     "SEC_REF_47" NUMBER,
     "SECN_47" VARCHAR2(88),
     "SEC_REF_48" NUMBER,
     "SECN_48" VARCHAR2(88),
     "SEC_REF_49" NUMBER,
     "SECN_49" VARCHAR2(88),
     "SEC_REF_50" NUMBER,
     "SECN_50" VARCHAR2(88),
     "SEC_REF_51" NUMBER,
     "SECN_51" VARCHAR2(88),
     "SEC_REF_52" NUMBER,
     "SECN_52" VARCHAR2(88),
     "SEC_REF_53" NUMBER,
     "SECN_53" VARCHAR2(88),
     "SEC_REF_54" NUMBER,
     "SECN_54" VARCHAR2(88),
     "SEC_REF_55" NUMBER,
     "SECN_55" VARCHAR2(88),
     "SEC_REF_56" NUMBER,
     "SECN_56" VARCHAR2(88),
     "SEC_REF_57" NUMBER,
     "SECN_57" VARCHAR2(88),
     "SEC_REF_58" NUMBER,
     "SECN_58" VARCHAR2(88),
     "SEC_REF_59" NUMBER,
     "SECN_59" VARCHAR2(88),
     "SEC_REF_60" NUMBER,
     "SECN_60" VARCHAR2(88),
     "SEC_REF_61" NUMBER,
     "SECN_61" VARCHAR2(88),
     "SEC_REF_62" NUMBER,
     "SECN_62" VARCHAR2(88),
     "SEC_REF_63" NUMBER,
     "SECN_63" VARCHAR2(88),
     "SEC_REF_64" NUMBER,
     "SECN_64" VARCHAR2(88),
     "SEC_REF_65" NUMBER,
     "SECN_65" VARCHAR2(88),
     "SEC_REF_66" NUMBER,
     "SECN_66" VARCHAR2(88),
     "SEC_REF_67" NUMBER,
     "SECN_67" VARCHAR2(88),
     "SEC_REF_68" NUMBER,
     "SECN_68" VARCHAR2(88),
     "SEC_REF_69" NUMBER,
     "SECN_69" VARCHAR2(88),
     "SEC_REF_70" NUMBER,
     "SECN_70" VARCHAR2(88),
     "SEC_REF_71" NUMBER,
     "SECN_71" VARCHAR2(88),
     "SEC_REF_72" NUMBER,
     "SECN_72" VARCHAR2(88),
     "SEC_REF_73" NUMBER,
     "SECN_73" VARCHAR2(88),
     "SEC_REF_74" NUMBER,
     "SECN_74" VARCHAR2(88),
     "SEC_REF_75" NUMBER,
     "SECN_75" VARCHAR2(88),
     "SEC_REF_76" NUMBER,
     "SECN_76" VARCHAR2(88),
     "SEC_REF_77" NUMBER,
     "SECN_77" VARCHAR2(88),
     "SEC_REF_78" NUMBER,
     "SECN_78" VARCHAR2(88),
     "SEC_REF_79" NUMBER,
     "SECN_79" VARCHAR2(88),
     "SEC_REF_80" NUMBER,
     "SECN_80" VARCHAR2(88),
     "SEC_REF_81" NUMBER,
     "SECN_81" VARCHAR2(88),
     "SEC_REF_82" NUMBER,
     "SECN_82" VARCHAR2(88),
     "SEC_REF_83" NUMBER,
     "SECN_83" VARCHAR2(88),
     "SEC_REF_84" NUMBER,
     "SECN_84" VARCHAR2(88),
     "SEC_REF_85" NUMBER,
     "SECN_85" VARCHAR2(88),
     "SEC_REF_86" NUMBER,
     "SECN_86" VARCHAR2(88),
     "SEC_REF_87" NUMBER,
     "SECN_87" VARCHAR2(88),
     "SEC_REF_88" NUMBER,
     "SECN_88" VARCHAR2(88),
     "SEC_REF_89" NUMBER,
     "SECN_89" VARCHAR2(88),
     "SEC_REF_90" NUMBER,
     "SECN_90" VARCHAR2(88),
     "SEC_REF_91" NUMBER,
     "SECN_91" VARCHAR2(88),
     "SEC_REF_92" NUMBER,
     "SECN_92" VARCHAR2(88),
     "SEC_REF_93" NUMBER,
     "SECN_93" VARCHAR2(88),
     "SEC_REF_94" NUMBER,
     "SECN_94" VARCHAR2(88),
     "SEC_REF_95" NUMBER,
     "SECN_95" VARCHAR2(88),
     "SEC_REF_96" NUMBER,
     "SECN_96" VARCHAR2(88),
     "SEC_REF_97" NUMBER,
     "SECN_97" VARCHAR2(88),
     "SEC_REF_98" NUMBER,
     "SECN_98" VARCHAR2(88),
     "SEC_REF_99" NUMBER,
     "SECN_99" VARCHAR2(88),
     "SEC_REF_100" NUMBER,
     "SECN_100" VARCHAR2(88),
     "SEC_REF_101" NUMBER,
     "SECN_101" VARCHAR2(88),
     "SEC_REF_102" NUMBER,
     "SECN_102" VARCHAR2(88),
     "SEC_REF_103" NUMBER,
     "SECN_103" VARCHAR2(88),
     "SEC_REF_104" NUMBER,
     "SECN_104" VARCHAR2(88),
     "SEC_REF_105" NUMBER,
     "SECN_105" VARCHAR2(88),
     "SEC_REF_106" NUMBER,
     "SECN_106" VARCHAR2(88),
     "SEC_REF_107" NUMBER,
     "SECN_107" VARCHAR2(88),
     "SEC_REF_108" NUMBER,
     "SECN_108" VARCHAR2(88),
     "SEC_REF_109" NUMBER,
     "SECN_109" VARCHAR2(88),
     "SEC_REF_110" NUMBER,
     "SECN_110" VARCHAR2(88),
     "SEC_REF_111" NUMBER,
     "SECN_111" VARCHAR2(88),
     "SEC_REF_112" NUMBER,
     "SECN_112" VARCHAR2(88),
     "SEC_REF_113" NUMBER,
     "SECN_113" VARCHAR2(88),
     "SEC_REF_114" NUMBER,
     "SECN_114" VARCHAR2(88),
     "SEC_REF_115" NUMBER,
     "SECN_115" VARCHAR2(88),
     "SEC_REF_116" NUMBER,
     "SECN_116" VARCHAR2(88),
     "SEC_REF_117" NUMBER,
     "SECN_117" VARCHAR2(88),
     "SEC_REF_118" NUMBER,
     "SECN_118" VARCHAR2(88),
     "SEC_REF_119" NUMBER,
     "SECN_119" VARCHAR2(88),
     "SEC_REF_120" NUMBER,
     "SECN_120" VARCHAR2(88),
     "SEC_REF_121" NUMBER,
     "SECN_121" VARCHAR2(88),
     "SEC_REF_122" NUMBER,
     "SECN_122" VARCHAR2(88),
     "SEC_REF_123" NUMBER,
     "SECN_123" VARCHAR2(88),
     "SEC_REF_124" NUMBER,
     "SECN_124" VARCHAR2(88),
     "SEC_REF_125" NUMBER,
     "SECN_125" VARCHAR2(88),
     "SEC_REF_126" NUMBER,
     "SECN_126" VARCHAR2(88),
     "SEC_REF_127" NUMBER,
     "SECN_127" VARCHAR2(88),
     "SEC_REF_128" NUMBER,
     "SECN_128" VARCHAR2(88),
     "SEC_REF_129" NUMBER,
     "SECN_129" VARCHAR2(88),
     "SEC_REF_130" NUMBER,
     "SECN_130" VARCHAR2(88),
     "SEC_REF_131" NUMBER,
     "SECN_131" VARCHAR2(88),
     "SEC_REF_132" NUMBER,
     "SECN_132" VARCHAR2(88),
     "SEC_REF_133" NUMBER,
     "SECN_133" VARCHAR2(88),
     "SEC_REF_134" NUMBER,
     "SECN_134" VARCHAR2(88),
     "SEC_REF_135" NUMBER,
     "SECN_135" VARCHAR2(88),
     "SEC_REF_136" NUMBER,
     "SECN_136" VARCHAR2(88),
     "SEC_REF_137" NUMBER,
     "SECN_137" VARCHAR2(88),
     "SEC_REF_138" NUMBER,
     "SECN_138" VARCHAR2(88),
     "SEC_REF_139" NUMBER,
     "SECN_139" VARCHAR2(88),
     "SEC_REF_140" NUMBER,
     "SECN_140" VARCHAR2(88),
     "SEC_REF_141" NUMBER,
     "SECN_141" VARCHAR2(88),
     "SEC_REF_142" NUMBER,
     "SECN_142" VARCHAR2(88),
     "SEC_REF_143" NUMBER,
     "SECN_143" VARCHAR2(88),
     "SEC_REF_144" NUMBER,
     "SECN_144" VARCHAR2(88),
     "SEC_REF_145" NUMBER,
     "SECN_145" VARCHAR2(88),
     "SEC_REF_146" NUMBER,
     "SECN_146" VARCHAR2(88),
     "SEC_REF_147" NUMBER,
     "SECN_147" VARCHAR2(88),
     "SEC_REF_148" NUMBER,
     "SECN_148" VARCHAR2(88),
     "SEC_REF_149" NUMBER,
     "SECN_149" VARCHAR2(88),
     "SEC_REF_150" NUMBER,
     "SECN_150" VARCHAR2(88),
     "SEC_REF_151" NUMBER,
     "SECN_151" VARCHAR2(88),
     "SEC_REF_152" NUMBER,
     "SECN_152" VARCHAR2(88),
     "SEC_REF_153" NUMBER,
     "SECN_153" VARCHAR2(88),
     "SEC_REF_154" NUMBER,
     "SECN_154" VARCHAR2(88),
     "SEC_REF_155" NUMBER,
     "SECN_155" VARCHAR2(88),
     "SEC_REF_156" NUMBER,
     "SECN_156" VARCHAR2(88),
     "SEC_REF_157" NUMBER,
     "SECN_157" VARCHAR2(88),
     "SEC_REF_158" NUMBER,
     "SECN_158" VARCHAR2(88),
     "SEC_REF_159" NUMBER,
     "SECN_159" VARCHAR2(88),
     "SEC_REF_160" NUMBER,
     "SECN_160" VARCHAR2(88),
     "SEC_REF_161" NUMBER,
     "SECN_161" VARCHAR2(88),
     "SEC_REF_162" NUMBER,
     "SECN_162" VARCHAR2(88),
     "SEC_REF_163" NUMBER,
     "SECN_163" VARCHAR2(88),
     "SEC_REF_164" NUMBER,
     "SECN_164" VARCHAR2(88),
     "SEC_REF_165" NUMBER,
     "SECN_165" VARCHAR2(88),
     "SEC_REF_166" NUMBER,
     "SECN_166" VARCHAR2(88),
     "SEC_REF_167" NUMBER,
     "SECN_167" VARCHAR2(88),
     "SEC_REF_168" NUMBER,
     "SECN_168" VARCHAR2(88),
     "SEC_REF_169" NUMBER,
     "SECN_169" VARCHAR2(88),
     "SEC_REF_170" NUMBER,
     "SECN_170" VARCHAR2(88),
     "SEC_REF_171" NUMBER,
     "SECN_171" VARCHAR2(88),
     "SEC_REF_172" NUMBER,
     "SECN_172" VARCHAR2(88),
     "SEC_REF_173" NUMBER,
     "SECN_173" VARCHAR2(88),
     "SEC_REF_174" NUMBER,
     "SECN_174" VARCHAR2(88),
     "SEC_REF_175" NUMBER,
     "SECN_175" VARCHAR2(88),
     "SEC_REF_176" NUMBER,
     "SECN_176" VARCHAR2(88),
     "SEC_REF_177" NUMBER,
     "SECN_177" VARCHAR2(88),
     "SEC_REF_178" NUMBER,
     "SECN_178" VARCHAR2(88),
     "SEC_REF_179" NUMBER,
     "SECN_179" VARCHAR2(88),
     "SEC_REF_180" NUMBER,
     "SECN_180" VARCHAR2(88),
     "SEC_REF_181" NUMBER,
     "SECN_181" VARCHAR2(88),
     "SEC_REF_182" NUMBER,
     "SECN_182" VARCHAR2(88),
     "SEC_REF_183" NUMBER,
     "SECN_183" VARCHAR2(88),
     "SEC_REF_184" NUMBER,
     "SECN_184" VARCHAR2(88),
     "SEC_REF_185" NUMBER,
     "SECN_185" VARCHAR2(88),
     "SEC_REF_186" NUMBER,
     "SECN_186" VARCHAR2(88),
     "SEC_REF_187" NUMBER,
     "SECN_187" VARCHAR2(88),
     "SEC_REF_188" NUMBER,
     "SECN_188" VARCHAR2(88),
     "SEC_REF_189" NUMBER,
     "SECN_189" VARCHAR2(88),
     "SEC_REF_190" NUMBER,
     "SECN_190" VARCHAR2(88),
     "SEC_REF_191" NUMBER,
     "SECN_191" VARCHAR2(88),
     "SEC_REF_192" NUMBER,
     "SECN_192" VARCHAR2(88),
     "SEC_REF_193" NUMBER,
     "SECN_193" VARCHAR2(88),
     "SEC_REF_194" NUMBER,
     "SECN_194" VARCHAR2(88),
     "SEC_REF_195" NUMBER,
     "SECN_195" VARCHAR2(88),
     "SEC_REF_196" NUMBER,
     "SECN_196" VARCHAR2(88),
     "SEC_REF_197" NUMBER,
     "SECN_197" VARCHAR2(88),
     "SEC_REF_198" NUMBER,
     "SECN_198" VARCHAR2(88),
     "SEC_REF_199" NUMBER,
     "SECN_199" VARCHAR2(88),
     "SEC_REF_200" NUMBER,
     "SECN_200" VARCHAR2(88),
     "SEC_REF_201" NUMBER,
     "SECN_201" VARCHAR2(88),
     "SEC_REF_202" NUMBER,
     "SECN_202" VARCHAR2(88),
     "SEC_REF_203" NUMBER,
     "SECN_203" VARCHAR2(88),
     "SEC_REF_204" NUMBER,
     "SECN_204" VARCHAR2(88),
     "SEC_REF_205" NUMBER,
     "SECN_205" VARCHAR2(88),
     "SEC_REF_206" NUMBER,
     "SECN_206" VARCHAR2(88),
     "SEC_REF_207" NUMBER,
     "SECN_207" VARCHAR2(88),
     "SEC_REF_208" NUMBER,
     "SECN_208" VARCHAR2(88)
   );Thank you for any help/advice.
Elie
Edited by: EEG on Jun 12, 2011 2:09 PM

So, is there some limit to the number of columns one can have in a "classic" or interactive report?Yes. See Oracle® Application Express Application Builder User's Guide Release 4.0, Appendix B: Oracle Application Express Limits.
Any idea why I would be getting this error?No, but I've replicated it in APEX 4.0.2.00.07 on 11.2.0.1.0 EE using a table of 420 <tt>varchar2(88)</tt> columns:
>
ORA-20503: Current version of data in database has changed since user initiated update process. current checksum = "50C9BDC0AA1AEF0EB272E9158B2117B4" application checksum = "0"
>
Happens whether using <tt>select *</tt> or including all column names in the query. (I know you don't want to type all the column names, but I'd never use <tt>select *</tt> in a production application: always use a proper column list. You can get one without typing by drag-and-drop of a table in most IDEs, or a query from <tt>user_tab_columns</tt>.)
I hit the problem at 274 columns. Such an arbitrary number leads me to think that the problem is not one of the number of columns per se, but is due to some other limit (possibly a 32K VARCHAR2/RAW buffer somewhere).
Workaround:
Updates to the report column attributes are actually being saved, and you can navigate them using the Page Definition tree view as described in Appendix B.
Getting More Help:
This is probably a bug. If you have a support agreement with Oracle raise an SR with Oracle Support.
Also:
<li>Search the forum using the "ORA-20503" code and other possible terms to see if there's anything relevant. I had a quick look but the only thread in this context recommended an upgrade on an Oracle 9 DB version that's not compatible with APEX 4.0.
<li>To get the attention of the Oracle APEX team or anyone else who may know more about this problem than we do, edit your original post and change the Subject to be more specific about the actual nature of the problem: <em>BUG? APEX 4.0: ORA-20503 error editing report with 400+ columns</em>, and include your database version/edition and the definition of the <tt>PVTAB</tt> table.
Finally:
Somebody's bound to ask, so we might as well get started:
<li>Why so many columns?
<li>What requirement is this trying to fulfil?

Getting ORA-12518 error with DG4ODBC for link with SQL Server

Hi all,
We have recently upgraded a test box to 11g2 on a 64bit windows platform and now when setting up our database links with our sql servers we are recieving an 'ORA-12518' error.
listener.ora
LISTENERPCIS =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = WILTS-ORCL4)(PORT = 1522))
SID_LIST_LISTENERPCIS =
(SID_LIST =
(SID_DESC =
(PROGRAM = dg4odbc)
(SID_NAME = PCIS)
(ORACLE_HOME = c:\oracle\product\11.2.0\db_1)
tnsnames.ora
PCIS =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = WILTS-ORCL4)(PORT = 1522))
(CONNECT_DATA =
(SID = PCIS)
(HS = OK)
Any help appericated
Cheers
David

C:\Users\administrator.ADMIN>tnsping pcis
TNS Ping Utility for 64-bit Windows: Version 11.2.0.1.0 - Production on 24-JUN-2
010 20:55:29
Copyright (c) 1997, 2010, Oracle. All rights reserved.
Used parameter files:
C:\ORACLE\PRODUCT\11.2.0\DBhome_1\network\admin\sqlnet.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = localhos
t)(PORT = 1522)) (CONNECT_DATA = (SID = PCIS)) (HS = OK))
OK (0 msec)
C:\Users\administrator.ADMIN>lsnrctl status LISTENERPCIS
LSNRCTL for 64-bit Windows: Version 11.2.0.1.0 - Production on 24-JUN-2010 20:55
:47
Copyright (c) 1991, 2010, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=localhost)(PORT=1522)))
STATUS of the LISTENER
Alias listenerpcis
Version TNSLSNR for 64-bit Windows: Version 11.2.0.1.0 - Produ
ction
Start Date 24-JUN-2010 20:55:17
Uptime 0 days 0 hr. 0 min. 30 sec
Trace Level admin
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File C:\ORACLE\PRODUCT\11.2.0\DBhome_1\network\admin\listen
er.ora
Listener Log File c:\oracle\product\11.2.0\diag\tnslsnr\WILTS-ORCL4\listenerpcis\alert\log.xml
Listener Trace File c:\oracle\product\11.2.0\diag\tnslsnr\WILTS-ORCL4\listenerpcis\trace\ora_12216_2424.trc
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=1522)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\PNPKEYipc)))
Services Summary...
Service "PCIS" has 1 instance(s).
Instance "PCIS", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
C:\Users\administrator.ADMIN>dg4odbc
Oracle Corporation --- THURSDAY JUN 24 2010 20:55:54.257
Heterogeneous Agent Release 11.2.0.1.0 - 64bit Production Built with
Oracle Database Gateway for ODBC
C:\Users\administrator.ADMIN>

ORA-00600 error in Oracle 10.1.0.5 database

Hi All,
Please help me to get rid of the below mentioned issue.
I am supporting a Oracle 10.1.0.5 prod database. we are getting a below ora-600 error message
ORA-00600: internal error code, arguments: [qerpxSlaveFetch1], [0], [], [], [], [], [], []
I have searched in metalink and there it is stated as bug with the product.
They adviced us to apply the Patch 3897688 or disable parallelism or Upgrade to the fixed release, 10gR2.
The patch 3897688 is not for window platform. Upgrade to 10gR2 is not possible in near future.
So please help me how to disable parallelism in 10g database.

ok fine satish will ask our development team to try your suggestion.
Can you please tell me whether the following init parameters we can use to disable parallelism?
PARALLEL_AUTOMATIC_TUNING = FALSE
PARALLEL_SERVER=FALSE (this alone will disable Parallel Execution)
PARALLEL_MIN_SERVERS=0 (this is additional restriction)
PARALLEL_MAX_SERVERS=0 (this is additional restriction)
Regards,
Aruna

ORA-30966: error detected in the XML Index layer

Dear all,
after upgrading from 9.2.0.8 to 11.2.0.1, Autoconfig ended with error:
Alert log file shows :
Mon Jul 04 21:33:50 2011
Errors in file /ebiz/oracle/diag/rdbms/vision/VISION/trace/VISION_ora_31642.trc (incident=16196):
+ORA-00600: internal error code, arguments: [kzxcInitLoadLocal-7], [64131], [ORA-64131: XMLIndex Metadata: failure during the looking up of the dictionary+
+ORA-30966: error detected in the XML Index layer+
+ORA-31011: XML parsing failed+
+ORA-01403: no data found+
+], [], [], [], [], [], [], [], [], []+
ORA-01403: no data found
Incident details in: /ebiz/oracle/diag/rdbms/vision/VISION/incident/incdir_16196/VISION_ora_31642_i16196.trc
Mon Jul 04 21:48:25 2011
Incremental checkpoint up to RBA [0x3b2.a445.0], current log tail at RBA [0x3b2.a447.0]
Mon Jul 04 21:49:25 2011
Errors in file /ebiz/oracle/diag/rdbms/vision/VISION/trace/VISION_ora_330.trc (incident=16206):
+ORA-00600: internal error code, arguments: [kzxcInitLoadLocal-7], [64131], [ORA-64131: XMLIndex Metadata: failure during the looking up of the dictionary+
+ORA-30966: error detected in the XML Index layer+
+ORA-31011: XML parsing failed+
for ORA-30966 i found one metalink document
Bug 9496480: XDB VIEWS INVALIDATED AFTER RUNNING CATUPGRD.SQL UPGRADING 9.2.0.8.0 TO 11.2.0.1I am not able to understand this bug detail, can some one help me to understand this BUG 9496480. Is it possible to run autoconfig ?RegardsHAMEED

This the result shows that ORACLE REAL APPLICATION CLUSTERS status is "INVALID" but we dont have any RAC configuration.!!!
SQL> select COMP_NAME,VERSION,STATUS from dba_registry;
COMP_NAME VERSION STATUS
Oracle Database Catalog Views 11.2.0.1.0 VALID
Oracle Database Packages and Types 11.2.0.1.0 VALID
Oracle Real Application Clusters 11.2.0.1.0 INVALID
JServer JAVA Virtual Machine 11.2.0.1.0 VALID
Oracle XDK 11.2.0.1.0 VALID
Oracle Database Java Packages 11.2.0.1.0 VALID
Oracle Multimedia 11.2.0.1.0 VALID
Spatial 11.2.0.1.0 VALID
Oracle Text 11.2.0.1.0 VALID
OLAP Analytic Workspace 11.2.0.1.0 VALID
Oracle OLAP API 11.2.0.1.0 VALID
OLAP Catalog 11.2.0.1.0 VALID
Oracle Data Mining 11.2.0.1.0 VALID
Oracle XML Database 11.2.0.1.0 VALID
14 rows selected.Kindly let me know what is the otherway !
Regards
HAMEED

ORA-12096: error in materialized view log on ORA-01301:insufficient privile

Hi,
One of our ebusiness Apps 11510 instances has database that was
upgraded from 9.2.0.6 to 10.2.0.4 with Database Vault.
After that, we are getting an error:
ORA-12096: error in materialized view log on "SCHEMA"."TABLE_NAME" ORA-01301:insufficient privileges
Can you please let know what can be the reason. Which user is being checked for the privileges?
Regards

I am facing the same issue in one of our internal instances.
Apps Environment has been upgraded from Database 9.2.0.6 to Database 10.2.0.4 with Database Vault. We started facing this issue and the same error after the upgrade. MLOG definition has not changed.
What privilege is it expecting to be present for the schema.
The definition of the MLOG is as given below
LOG_TRIGGER = NULL
ROWIDS = YES
PRIMARY_KEY = NO
OBJECT_ID = NO
FILTER_COLUMNS = NO
SEQUENCE = NO
INCLUDE_NEW_VALUES = NO

ORA 03114 error

ORA 03114 error
weblogic
Forms 11g
db 11g
winserver 2008 64 bit

I am sorry I didn't explain my problem Clearly
My system developed with oracle forms 10g & oracle database 10g
Using oracle application server 10g with win server 2003 32 bit
And It was works properly
Now I upgrade my system to oracle database 11g and weblogic 11g
with win server2008 64 bit
and I tested it it is work no problems but som times when i run my application
if give me this error
frm-40735 unhandled exception ora-03114
and ask for the username and password for database when I give it is give the same error
if I close my Browser and wait sometimes and try agine it is work
why this error happen ………………………….??????
If anyone can help I would be grateful to him .
Thanks

11.1 to 11.2 upgrade - ORA-25319 errors

Similar Messages

Maybe you are looking for