Home » RDBMS Server » Enterprise Manager » Cannot start dbconsole after upgrading both rdbms and db version (11.2.0.4 SE, Windows Server 2012 r2)
| Cannot start dbconsole after upgrading both rdbms and db version [message #653830] |
Tue, 19 July 2016 22:38  |
 |
juniordbanewbie
Messages: 250
Registered: April 2014
|
Senior Member |
|
|
Dear all,
I cannot start dbconsole after upgrading both rdbms and db version. Old box run 11.2.0.2 SE on windows 2008 r2 while new box initially run 11.2.0.2 SE on windows 2012 r2
here's the upgrade is done:
install 11.2.0.2 on windows 2012 r2 box,
shutdown db cleanly in old box running windows 2008 r2
unmount the drives from the old box
mount the drives from the old box to the new box.
upgrade db to 11.2.0.4
I've already reconfigure dbconsole, but it always cannot start up. here the error in the %ORACLE_HOME%/%HOSTNAME%_%ORACLE_SID%/sysman/log/emagent.trc
2016-07-19 04:28:51,423 Thread-1256 ERROR ssl: nzos_Handshake failed, ret=29024
2016-07-19 04:28:51,423 Thread-1256 ERROR http: 788: Unable to initialize ssl connection with server, aborting connection attempt
2016-07-19 04:28:51,423 Thread-1256 ERROR pingManager: nmepm_pingReposURL: Cannot connect to https://hou-ora.camden.com:1158/em/upload/: retStatus=-1
2016-07-19 04:28:51,423 Thread-1256 WARN main: clear collection state due to OMS_version difference
2016-07-19 04:28:51,439 Thread-1256 WARN command: Job Subsystem Timeout set at 600 seconds
2016-07-19 04:28:51,439 Thread-1256 WARN upload: Upload manager has no Failure script: disabled
2016-07-19 04:28:51,470 Thread-1256 WARN metadata: Metric VirtualHosts does not have any data columns
2016-07-19 04:28:51,486 Thread-1256 WARN metadata: Metric collectSnapshot does not have any data columns
2016-07-19 04:28:51,564 Thread-1256 WARN metadata: Metric hung_system_traces does not have any data columns
2016-07-19 04:28:51,736 Thread-4628 WARN TargetManager: Query returned 0 rows (only one expected) for the dynamic property from_cluster
2016-07-19 04:28:58,923 Thread-1256 WARN TargetManager: Regenerating all Metadata
2016-07-19 04:28:59,876 Thread-1256 WARN upload: Truncating value of "SHORT_NAME" from "Average Synchronous Single-Block Read Latency (ms)" to "Average Synchronous Single-Block Read La"
2016-07-19 04:28:59,892 Thread-1256 WARN upload: Truncating value of "SHORT_NAME" from "Average Synchronous Single-Block Read Latency (ms)" to "Average Synchronous Single-Block Read La"
2016-07-19 04:29:01,142 Thread-1256 WARN upload: Truncating value of "COLUMN_LABEL" from "Total messages processed per queue per subscriber per minute in the last interval" to "Total messages processed per queue per subscriber per minute in "
2016-07-19 04:29:01,142 Thread-1256 WARN upload: Truncating value of "COLUMN_LABEL" from "Total messages received per queue per subscriber per minute in the last interval" to "Total messages received per queue per subscriber per minute in t"
2016-07-19 04:29:01,158 Thread-1256 WARN upload: Truncating value of "COLUMN_LABEL" from "Messages processed per queue (%) per subscriber per minute in the last interval" to "Messages processed per queue (%) per subscriber per minute in th"
2016-07-19 04:29:01,173 Thread-1256 WARN upload: Truncating value of "COLUMN_LABEL" from "Age of the first message in persistent queue per subscriber (seconds)" to "Age of the first message in persistent queue per subscriber (sec"
2016-07-19 04:29:01,173 Thread-1256 WARN upload: Truncating value of "COLUMN_LABEL" from "Age of the first message in the buffered queue per queue (seconds)" to "Age of the first message in the buffered queue per queue (second"
2016-07-19 04:29:01,470 Thread-1256 WARN collector: the column name first_message_age in this condition does not exist in metric aq_msgs_persistentq_per_subscriber
2016-07-19 04:29:01,486 Thread-1256 WARN collector: Regenerating all DefaultColls
2016-07-19 04:29:04,720 Thread-1256 WARN collector: the column name first_message_age in this condition does not exist in metric aq_msgs_persistentq_per_subscriber
2016-07-19 04:29:05,033 Thread-2868 WARN recvlets.aq: no matching registered alert type for instance_efficiency.pxdwngrd_ps
2016-07-19 04:29:05,033 Thread-2868 WARN recvlets.aq: no matching registered alert type for instance_efficiency.pxdwngrdserial_pt
2016-07-19 04:29:05,033 Thread-2868 WARN recvlets.aq: no matching registered alert type for wait_bottlenecks.userio_wait_cnt
2016-07-19 04:29:05,033 Thread-2868 WARN recvlets.aq: no matching registered alert type for wait_bottlenecks.other_wait_cnt
Have attempt solution in ---> DB Console 10g HTTPS (SSL) Certificate Has Expired. Error "ssl: nzos_Handshake failed, ret=29024" Encountered in Emagent Logs ( Doc ID 738659.1 )
but still not working.
thanks in advance!
|
|
|
|
| Re: Cannot start dbconsole after upgrading both rdbms and db version [message #653871 is a reply to message #653830] |
Thu, 21 July 2016 01:09  |
|
juniordbanewbie
Messages: 250
Registered: April 2014
|
Senior Member |
|
|
Dear Sirs,
I've resolve this issue myself. For the benefit of those who encounter the problems as me and when the log makes who sense of the situation, here the solution.
First look at what process is locking on to 1158 by the following command
windows/dos
netstat -ano | find "1158"
linux
netstat -ano | grep "1158"
this will give u the pid or process id of the process the is holding on to port 1158
next found out from the task manager which process is holding on to port 1158.
I realize that %OLD_ORACLE_HOME%\jdk\bin\java.exe is locking on to the port 1158.
The reason why %OLD_ORACLE_HOME%\jdk\bin\java.exe is locking on to the port 1158 is as follow:
emca upgrade is not executed, meaning OracleDBConsole%ORACLE_SID% will always start from the old ORACLE_HOME
OracleDBConsole%ORACLE_SID% is set to autostart
=>it means that OracleDBConsole%ORACLE_SID% will always autostart and it will be from the old %ORACLE_HOME%.
if the log doesn't make sense as in my case, go to the basic fundamentals, like why cannot startup, why cannot startup with port 1158, who is locking on to port 1158
|
|
|
|
Goto Forum:
Current Time: Fri Nov 22 17:48:15 CST 2024
|
] 
Blog
Search
Help
Members
Register
Login
Home
