FranklinFaces.com - Oracle & SQL Server Database Forums for all IT Professionals / Oracle Forum / ORA - Oracle Database Error Codes - Search via specific error codes. / Non-Coded Errors and Alerts

EMD upload error: uploadXMLFiles skipped :: OMS version not checked yet..

Admin — Tue, 21 Jul 2009 12:29:50 GMT

I get the following error when trying to upload. the agent is up and running fine and i stopped and started it again and still getting the message:

#[OEMAGT]-> emctl upload
Oracle Enterprise Manager 10g Release 3 Grid Control 10.2.0.3.0.
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
---------------------------------------------------------------
EMD upload error: uploadXMLFiles skipped :: OMS version not checked yet..

My agent is running fine:

#[OEMAGT]-> emctl status agent
Oracle Enterprise Manager 10g Release 3 Grid Control 10.2.0.3.0.
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
---------------------------------------------------------------
Agent Version : 10.2.0.3.0
OMS Version : 10.2.0.4.0
Protocol Version : 10.2.0.2.0
Agent Home : /oracle/product/10.2.0/oem_1/agent10g
Agent binaries : /oracle/product/10.2.0/oem_1/agent10g
Agent Process ID : 11484
Parent Process ID : 11478
Agent URL : https://njprodpdb02:3872/emd/main/
Repository URL : https://dcprodspdba01:1159/em/upload
Started at : 2009-07-20 16:28:49
Started by user : oracle
Last Reload : 2009-07-20 16:28:49
Last successful upload : (none)
Last attempted upload : (none)
Total Megabytes of XML files uploaded so far : 0.00
Number of XML files pending upload : 96
Size of XML files pending upload(MB) : 12.02
Available disk space on upload filesystem : 36.97%
Last attempted heartbeat to OMS : 2009-07-21 12:15:56
Last successful heartbeat to OMS : unknown
---------------------------------------------------------------
Agent is Running and Ready

I did the following to solve this:

#[OEMAGT]-> emctl stop agent
Oracle Enterprise Manager 10g Release 3 Grid Control 10.2.0.3.0.
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
Stopping agent ... stopped.

#[OEMAGT]-> emctl unsecure agent
Oracle Enterprise Manager 10g Release 3 Grid Control 10.2.0.3.0.
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
Checking Agent for HTTP... Done.
Agent is already stopped... Done.
Unsecuring agent... Started.
Agent is now unsecured... Done.
Unsecuring agent... Ended.

#[OEMAGT]-> emctl secure agent
Oracle Enterprise Manager 10g Release 3 Grid Control 10.2.0.3.0.
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
Enter Agent Registration password :
Agent is already stopped... Done.
Securing agent... Started.
Requesting an HTTPS Upload URL from the OMS... Done.
Requesting an Oracle Wallet and Agent Key from the OMS... Done.
Check if HTTPS Upload URL is accessible from the agent... Done.
Configuring Agent for HTTPS in CENTRAL_AGENT mode... Done.
EMD_URL set in /oracle/product/10.2.0/oem_1/agent10g/sysman/config/emd.properties
Securing agent... Successful.

#[OEMAGT]-> emctl start agent
Oracle Enterprise Manager 10g Release 3 Grid Control 10.2.0.3.0.
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
Starting agent ........ started.

I hope this helps .

Thanks,

ksvcreate: Process(m000) creation failed

Admin — Wed, 25 Feb 2009 01:39:50 GMT

OK, so we're seeing so many of these in the alert log.

Tue Feb 24 22:10:34 2009
Process m000 died, see its trace file
Tue Feb 24 22:10:34 2009
ksvcreate: Process(m000) creation failed
Tue Feb 24 22:11:35 2009
Process m000 died, see its trace file
Tue Feb 24 22:11:35 2009
ksvcreate: Process(m000) creation failed
Tue Feb 24 22:12:36 2009
Process m000 died, see its trace file
Tue Feb 24 22:12:36 2009
ksvcreate: Process(m000) creation failed
Tue Feb 24 22:13:37 2009
Process m000 died, see its trace file
Tue Feb 24 22:13:37 2009
ksvcreate: Process(m000) creation failed
Tue Feb 24 22:14:38 2009
Process m000 died, see its trace file
Tue Feb 24 22:14:38 2009
ksvcreate: Process(m000) creation failed
Tue Feb 24 22:15:39 2009
Process m000 died, see its trace file
Tue Feb 24 22:15:39 2009
ksvcreate: Process(m000) creation failed
Tue Feb 24 22:16:41 2009
Process m000 died, see its trace file
Tue Feb 24 22:16:41 2009
ksvcreate: Process(m000) creation failed
Tue Feb 24 22:17:42 2009
Process m000 died, see its trace file
Tue Feb 24 22:17:42 2009
ksvcreate: Process(m000) creation failed
Tue Feb 24 22:18:43 2009
Process m000 died, see its trace file
Tue Feb 24 22:18:43 2009
ksvcreate: Process(m000) creation failed
Tue Feb 24 22:46:55 2009
Tue Feb 24 23:00:14 2009
Process m000 died, see its trace file

Not sure what's causing this initially but we eventually figured it out because we couldn't get into the database using sqlplus '/ as sysdba';

It turned out that the max processes of 400 had been reached and no new processes were able to connect to the database.

After verifying that all users were having this issue, we decided to bounce the database and update the processes parameter to 900.

Make sure you have enough memory + your OS parameters are set properly before bumping up any parameters. In our case we had sufficient and all went well.

You may want to open up a Tar with oracle if you have support in case this step didn't work. There maybe a bug you could be hitting.

Good luck and let me know how you guys make out.

Regards,

WARNING: Subscription for node down event still pending

Admin — Sun, 18 Jan 2009 09:51:41 GMT

Thread: WARNING: Subscription for node down event still pending? Urgent!

"WARNING: Subscription for node down event still pending"

any help on this ...very urgent please
this is running on linux fedora and 10g .. never ever had this problem before.

"jdbcclient" in V$session

Admin — Wed, 26 May 2010 10:18:36 GMT

I noticed in v$session, some of the sessions have "jdbcclient" under MACHINE column and "JDBC-1.0-Client" under PROGRAM column. I've searched through metalink, but found no one so far can really find a way to identify the source of these sessions. Some of the metalink posts said prior to 8.1.7, there is no way to identify where the sessions come from. However, I have 10.2.0.3 running on Red Hat Linux and I still see the same thing.

Is there anyone who has a way to identify which machines the sessions come from?

WARNING: Oracle executable binary mismatch detected.

Admin — Sun, 01 Nov 2009 13:36:46 GMT

The OS admin applied OS Patch and after the reboot, the db came up fine but there were tons of messages in alert log:

Sun Nov 1 10:02:22 2009
Completed: ALTER DATABASE OPEN
Sun Nov 1 10:10:01 2009
WARNING: Oracle executable binary mismatch detected.
Binary of new process does not match binary which started instance
issue alter system set "_disable_image_check" = true to disable these messages
WARNING: Oracle executable binary mismatch detected.
Binary of new process does not match binary which started instance
issue alter system set "_disable_image_check" = true to disable these messages
WARNING: Oracle executable binary mismatch detected.
Binary of new process does not match binary which started instance
issue alter system set "_disable_image_check" = true to disable these messages
WARNING: Oracle executable binary mismatch detected.
Binary of new process does not match binary which started instance
issue alter system set "_disable_image_check" = true to disable these messages
WARNING: Oracle executable binary mismatch detected.
Binary of new process does not match binary which started instance
issue alter system set "_disable_image_check" = true to disable these messages
WARNING: Oracle executable binary mismatch detected.
Binary of new process does not match binary which started instance
issue alter system set "_disable_image_check" = true to disable these messages
WARNING: Oracle executable binary mismatch detected.
Binary of new process does not match binary which started instance
issue alter system set "_disable_image_check" = true to disable these messages
WARNING: Oracle executable binary mismatch detected.
Binary of new process does not match binary which started instance
issue alter system set "_disable_image_check" = true to disable these messages
WARNING: Oracle executable binary mismatch detected.
Binary of new process does not match binary which started instance
issue alter system set "_disable_image_check" = true to disable these messages
WARNING: Oracle executable binary mismatch detected.
Binary of new process does not match binary which started instance
issue alter system set "_disable_image_check" = true to disable these messages
WARNING: Oracle executable binary mismatch detected.
Binary of new process does not match binary which started instance
issue alter system set "_disable_image_check" = true to disable these messages
WARNING: Oracle executable binary mismatch detected.
Binary of new process does not match binary which started instance
issue alter system set "_disable_image_check" = true to disable these messages
WARNING: Oracle executable binary mismatch detected.
Binary of new process does not match binary which started instance
issue alter system set "_disable_image_check" = true to disable these messages
Sun Nov 1 10:26:26 2009

Couldn't find much on the internet other then to open up tar with oracle. In metalink couldn't find much info, then one of my co-workers mentioned that this is a known thing on hp servers. Not sure why this does it the way it does.

Here is the info on the system:

HP-UX hpdnp290 B.11.11 U 9000/800 3154283422 unlimited-user license
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production

I had to shutdown the database and issue relink all command to fix this issue.

So basically follow these steps:

1. Shutdown immediate

2. Stop listener

3. relink all

4. start db

5. start listener.

Hope this helps you out.

Thanks,

Distributed Transactions - Errors - In Doubt Transactions

Admin — Wed, 14 Jan 2009 23:49:16 GMT

So I noticed the following in the alert log for which I have no clue on how to do .

The users were complaining that they had application issue but the database seemed to be fine and connections were ok and other users were ok but the distributed transactions were the ones having problems. I didn't know what to do.

DISTRIB TRAN bea1.1B1ACBD08DDDC3D5B838
is local tran 1.44.168955 (hex=01.2c.293fb)
insert pending prepared tran, scn=10251917462492 (hex=952.f5e60bdc)
DISTRIB TRAN bea1.0F11E80A89A25DB12D9B
is local tran 2.27.266178 (hex=02.1b.40fc2)
insert pending prepared tran, scn=10251917462490 (hex=952.f5e60bda)
DISTRIB TRAN bea1.13A0807B8F33B4D288AE
is local tran 6.15.190782 (hex=06.0f.2e93e)
insert pending prepared tran, scn=10251917868003 (hex=952.f5ec3be3)
DISTRIB TRAN bea1.13A2807B8F33B4D288AE
is local tran 8.26.211463 (hex=08.1a.33a07)
insert pending prepared tran, scn=10251917867952 (hex=952.f5ec3bb0)
DISTRIB TRAN bea1.0F352E5D72CC2AB61D0D
is local tran 9.19.232071 (hex=09.13.38a87)
insert pending prepared tran, scn=10251917879005 (hex=952.f5ec66dd)
DISTRIB TRAN bea1.13A4807B8F33B4D288AE
is local tran 10.8.228017 (hex=0a.08.37ab1)
insert pending prepared tran, scn=10251917867950 (hex=952.f5ec3bae)
DISTRIB TRAN bea1.13A3807B8F33B4D288AE
is local tran 13.29.162036 (hex=0d.1d.278f4)
insert pending prepared tran, scn=10251917867985 (hex=952.f5ec3bd1)
Wed Jan 14 00:21:08 2009
DISTRIB TRAN bea1.0F11E80A89A25DB12D9B
is local tran 2.27.266178 (hex=02.1b.40fc2)
change pending prepared tran, scn=10251917462490 (hex=952.f5e60bda)
to pending collecting tran, scn=10251917462490 (hex=952.f5e60bda)
DISTRIB TRAN bea1.0F11E80A89A25DB12D9B
is local tran 2.27.266178 (hex=02.1b.40fc2))
delete pending collecting tran, scn=10251917462490 (hex=952.f5e60bda)
Wed Jan 14 00:21:53 2009
DISTRIB TRAN bea1.0F19E80A89A25DB12D9B
is local tran 15.18.185684 (hex=0f.12.2d554)
change pending prepared tran, scn=10251917463595 (hex=952.f5e6102b)
to pending collecting tran, scn=10251917463595 (hex=952.f5e6102b)
DISTRIB TRAN bea1.0F19E80A89A25DB12D9B
is local tran 15.18.185684 (hex=0f.12.2d554))
delete pending collecting tran, scn=10251917463595 (hex=952.f5e6102b)
Wed Jan 14 00:21:55 2009
DISTRIB TRAN bea1.1B1ACBD08DDDC3D5B838
is local tran 1.44.168955 (hex=01.2c.293fb)
change pending prepared tran, scn=10251917462492 (hex=952.f5e60bdc)
to pending collecting tran, scn=10251917462492 (hex=952.f5e60bdc)
DISTRIB TRAN bea1.1B1ACBD08DDDC3D5B838
is local tran 1.44.168955 (hex=01.2c.293fb))
delete pending collecting tran, scn=10251917462492 (hex=952.f5e60bdc)
Wed Jan 14 00:21:58 2009
DISTRIB TRAN bea1.0EEA8F1DC033C4B87C21
is local tran 30.37.180674 (hex=1e.25.2c1c2)
change pending prepared tran, scn=10251917467013 (hex=952.f5e61d85)
to pending collecting tran, scn=10251917467013 (hex=952.f5e61d85)
DISTRIB TRAN bea1.0EEA8F1DC033C4B87C21
is local tran 30.37.180674 (hex=1e.25.2c1c2))
delete pending collecting tran, scn=10251917467013 (hex=952.f5e61d85)
Wed Jan 14 00:22:09 2009
DISTRIB TRAN bea1.106EFC4D055B5ADCE982
is local tran 17.6.153054 (hex=11.06.255de)
change pending prepared tran, scn=10251917497020 (hex=952.f5e692bc)
to pending collecting tran, scn=10251917497020 (hex=952.f5e692bc)
DISTRIB TRAN bea1.106EFC4D055B5ADCE982
is local tran 17.6.153054 (hex=11.06.255de))
delete pending collecting tran, scn=10251917497020 (hex=952.f5e692bc)
Wed Jan 14 00:22:40 2009
DISTRIB TRAN bea1.1B22CBD08DDDC3D5B838
is local tran 29.33.176598 (hex=1d.21.2b1d6)
change pending prepared tran, scn=10251917589948 (hex=952.f5e7fdbc)
to pending collecting tran, scn=10251917589948 (hex=952.f5e7fdbc)
DISTRIB TRAN bea1.1B22CBD08DDDC3D5B838
is local tran 29.33.176598 (hex=1d.21.2b1d6))
delete pending collecting tran, scn=10251917589948 (hex=952.f5e7fdbc)
Wed Jan 14 00:22:43 2009
DISTRIB TRAN bea1.0F262E5D72CC2AB61D0D
is local tran 32.39.143275 (hex=20.27.22fab)
change pending prepared tran, scn=10251917596126 (hex=952.f5e815de)
to pending collecting tran, scn=10251917596126 (hex=952.f5e815de)
DISTRIB TRAN bea1.0F262E5D72CC2AB61D0D
is local tran 32.39.143275 (hex=20.27.22fab))
delete pending collecting tran, scn=10251917596126 (hex=952.f5e815de)
Wed Jan 14 00:24:13 2009
DISTRIB TRAN bea1.0F352E5D72CC2AB61D0D
is local tran 9.19.232071 (hex=09.13.38a87)
change pending prepared tran, scn=10251917879005 (hex=952.f5ec66dd)
to pending collecting tran, scn=10251917879005 (hex=952.f5ec66dd)
DISTRIB TRAN bea1.0F352E5D72CC2AB61D0D
is local tran 9.19.232071 (hex=09.13.38a87))
delete pending collecting tran, scn=10251917879005 (hex=952.f5ec66dd)

Anyone have any clue ? I did a google search but no luck.

Fatal NI connect error 12547, connecting to:

Admin — Sun, 19 Apr 2009 10:33:50 GMT

I'm getting the following after upgrading and then having to back out of the upgrade when connecting to the db from the application user that resides on the same server as the database.

DB: 10.2.0.3.0

OS: AIX 3.5

***********************************************************************

Fatal NI connect error 12547, connecting to:

(DESCRIPTION=(ADDRESS=(PROTOCOL=beq)(PROGRAM=/opt/oracle/10.2/bin/oracle)(ARGV0=oraclemarchm52)(ARGS='(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))')(DETACH=NO))(CONNECT_DATA=(CID=(PROGRAM=admin@prodsrv)(HOST=prodsrv)(USER=admin))))

VERSION INFORMATION:

TNS for IBM/AIX RISC System/6000: Version 10.2.0.3.0 - Production

Oracle Bequeath NT Protocol Adapter for IBM/AIX RISC System/6000: Version 10.2.0.3.0 - Production

TCP/IP NT Protocol Adapter for IBM/AIX RISC System/6000: Version 10.2.0.3.0 - Production

Time: 19-APR-2009 04:45:47

Tracing not turned on.

Tns error struct:

ns main err code: 12547

TNS-12547: TNS:lost contact

ns secondary err code: 12560

nt main err code: 517

TNS-00517: Lost contact

nt secondary err code: 32

nt OS err code: 0

***********************************************************************

The way this was resolved was by shutting down all applications, databases, and listeners. Then did a relink all.

After that, we started up all the databases, listener, and then the application and it was ok after wards.

Hope this helps.

tnsping 553476 : map : Permission Denied

Admin — Sun, 19 Apr 2009 10:24:42 GMT

I've been getting the following error message when issuing the tnsping command:

$ tnsping proddb52

553476 : map : Permission Denied

TNS Ping Utility for IBM/AIX RISC System/6000: Version 10.2.0.3.0 - Production on 19-APR-2009 07:34:45

Used parameter files:

Used TNSNAMES adapter to resolve the alias

Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP) (HOST = prodsrv-db2) (PORT = 1521))) (CONNECT_DATA = (SID = proddb52)))

OK (0 msec)

The way i resolved to stopp the Permission denied message is to run the following:

$ORACLE_HOME/install/changePerm.sh as the oracle user. If this still doesn't work, then run the following manually:

chmod 755 $ORACLE_HOME/bin/sqlplus

chmod 751 $ORACLE_HOME/bin/lsnrctl

Once you do this, just restart the listener and the message should go away .

Thanks,

Some indexes or index [sub]partitions of table SYS.WRH$_SQLSTAT have been marked unusable

Admin — Thu, 26 Mar 2009 01:24:26 GMT

Out of nowhere we start seeing a bunch of messages in the alert log:

Tue Mar 24 22:02:34 2009
Some indexes or index [sub]partitions of table SYS.WRH$_SQLSTAT have been marked unusable
Tue Mar 24 22:04:42 2009
Completed checkpoint up to RBA [0x2d83.2.10], SCN: 10386207811326
Tue Mar 24 22:29:46 2009
Incremental checkpoint up to RBA [0x2d83.482eef.0], current log tail at RBA [0x2d83.51930f.0]
Tue Mar 24 23:00:12 2009
Incremental checkpoint up to RBA [0x2d83.727e0d.0], current log tail at RBA [0x2d83.762401.0]
Tue Mar 24 23:09:52 2009
Beginning log switch checkpoint up to RBA [0x2d84.2.10], SCN: 10386208010755
Thread 1 advanced to log sequence 11652

Then soon after:

Wed Mar 25 22:45:07 2009
Errors in file /opt/dbms/app/oracle/admin/PROD200P/udump/prod200p_ora_28403.trc:
ORA-00600: internal error code, arguments: [kcbnew_3], [0], [8], [195539], [], [], [], []
Wed Mar 25 22:48:06 2009
statement in resumable session 'User QBISOP(146), Session 188, Instance 1' was aborted
Wed Mar 25 22:51:03 2009
Errors in file /opt/dbms/app/oracle/admin/PROD200P/udump/prod200p_ora_28309.trc:
ORA-00600: internal error code, arguments: [kcbnew_3], [0], [8], [195534], [], [], [], []
Wed Mar 25 22:51:05 2009

As per the metalink doc id 430446.1 following are the solutions that are possible

These messages should be considered a warning and not something harmful to the database.

SOLUTION:
1) This message can be ignored as it is considered as a warning.

OR

2) Disable MMON from gathering stats:

dbms_workload_repository.modify_snapshot_settings(interval=>0);

OR

3) Partition the offending table WRH$_SQLSTAT into sysaux tablespace.

Metalink link: 430446.1

Symptoms

Lots of messages in alert log file like:

Mon Apr 23 23:25:40 2007
Some indexes or index [sub]partitions of table SYS.WRH$_SQLSTAT have been marked unusable
Tue Apr 24 01:26:11 2007

Cause

These messages are generated when AWR runs a space management routine in which AWR tables are moved out from the system tablespace to sysaux tablespace.

For some AWR tables, just after table is moved, indexes are marked "unusable". Thats when these messaged are generated.

Solution
These messages should be considered a warning and not something harmful to the database.
SOLUTION:
1) This message can be ignored as it is considered as a warning.
OR

2) Disable MMON from gathering stats:
dbms_workload_repository.modify_snapshot_settings(interval=>0);

OR
3) Partition the offending table WRH$_SQLSTAT into sysaux tablespace.

Hope this helps.