Skip to Main Content

Integration

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Weblogic Server Failed to start! Help!

850366Mar 25 2011 — edited Apr 1 2011
So, the problem in header, as you can see.

Maybe I done incorrect configuration, or something.

Here is log:


####<25.03.2011 19:09:42 YEKT> <Info> <WebLogicServer> <vpc> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1301062182145> <BEA-000000> <WebLogic Server "AdminServer" version:
WebLogic Server 10.3.4.0 Fri Dec 17 20:47:33 PST 2010 1384255 Copyright (c) 1995, 2009, Oracle and/or its affiliates. All rights reserved.>
####<25.03.2011 19:09:42 YEKT> <Notice> <Log Management> <vpc> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1301062182225> <BEA-170019> <The server log file C:\Oracle\Middleware\user_projects\domains\base_domain\servers\AdminServer\logs\AdminServer.log is opened. All server side log events will be written to this file.>
####<25.03.2011 19:09:42 YEKT> <Info> <Log Management> <vpc> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1301062182225> <BEA-170023> <The Server Logging is initialized with Java Logging API implementation.>
####<25.03.2011 19:09:42 YEKT> <Info> <Diagnostics> <vpc> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1301062182305> <BEA-320001> <The ServerDebug service initialized successfully.>
####<25.03.2011 19:09:42 YEKT> <Info> <Server> <vpc> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1301062182415> <BEA-002622> <The protocol "t3" is now configured.>
####<25.03.2011 19:09:42 YEKT> <Info> <Server> <vpc> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1301062182415> <BEA-002622> <The protocol "t3s" is now configured.>
####<25.03.2011 19:09:42 YEKT> <Info> <Server> <vpc> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1301062182425> <BEA-002622> <The protocol "http" is now configured.>
####<25.03.2011 19:09:42 YEKT> <Info> <Server> <vpc> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1301062182425> <BEA-002622> <The protocol "https" is now configured.>
####<25.03.2011 19:09:42 YEKT> <Info> <Server> <vpc> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1301062182425> <BEA-002622> <The protocol "iiop" is now configured.>
####<25.03.2011 19:09:42 YEKT> <Info> <Server> <vpc> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1301062182425> <BEA-002622> <The protocol "iiops" is now configured.>
####<25.03.2011 19:09:42 YEKT> <Info> <Server> <vpc> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1301062182425> <BEA-002622> <The protocol "ldap" is now configured.>
####<25.03.2011 19:09:42 YEKT> <Info> <Server> <vpc> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1301062182425> <BEA-002622> <The protocol "ldaps" is now configured.>
####<25.03.2011 19:09:42 YEKT> <Info> <Server> <vpc> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1301062182425> <BEA-002622> <The protocol "cluster" is now configured.>
####<25.03.2011 19:09:42 YEKT> <Info> <Server> <vpc> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1301062182425> <BEA-002622> <The protocol "clusters" is now configured.>
####<25.03.2011 19:09:42 YEKT> <Info> <Server> <vpc> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1301062182435> <BEA-002622> <The protocol "snmp" is now configured.>
####<25.03.2011 19:09:42 YEKT> <Info> <Server> <vpc> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1301062182435> <BEA-002622> <The protocol "admin" is now configured.>
####<25.03.2011 19:09:42 YEKT> <Info> <Server> <vpc> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1301062182435> <BEA-002624> <The administration protocol is "t3s" and is now configured.>
####<25.03.2011 19:09:42 YEKT> <Info> <RJVM> <vpc> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1301062182445> <BEA-000570> <Network Configuration for Channel "AdminServer"
Listen Address localhost:7001
Public Address N/A
Http Enabled true
Tunneling Enabled false
Outbound Enabled false
Admin Traffic Enabled true>
####<25.03.2011 19:09:42 YEKT> <Info> <Server> <vpc> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1301062182475> <BEA-002609> <Channel Service initialized.>
####<25.03.2011 19:09:42 YEKT> <Info> <Socket> <vpc> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1301062182536> <BEA-000406> <NTSocketMuxer was built on Jan 13 2005 17:47:03
>
####<25.03.2011 19:09:42 YEKT> <Info> <Socket> <vpc> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1301062182576> <BEA-000436> <Allocating 2 reader threads.>
####<25.03.2011 19:09:42 YEKT> <Info> <Socket> <vpc> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1301062182576> <BEA-000446> <Native IO Enabled.>
####<25.03.2011 19:09:42 YEKT> <Info> <IIOP> <vpc> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1301062182696> <BEA-002014> <IIOP subsystem enabled.>
####<25.03.2011 19:09:43 YEKT> <Info> <Security> <vpc> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1301062183527> <BEA-000000> <Starting BEA Kodo 4.2.0>
####<25.03.2011 19:09:43 YEKT> <Info> <Security> <vpc> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1301062183587> <BEA-000000> <Using dictionary class "kodo.jdbc.sql.KodoOracleDictionary".>
####<25.03.2011 19:09:44 YEKT> <Info> <Security> <vpc> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1301062184038> <BEA-000000> <OpenJPA is now connecting to the database in order to figure out what JDBC driver you are using, as OpenJPA must alter its behavior for this database depending on the driver vendor. To avoid this connection, set the DriverVendor value in your openjpa.jdbc.DBDictionary configuration property to one of the following values:
oracle, oracle92 (for the 9.2 driver), datadirect, datadirect61 (for driver versions <= 3.1), other
For example:
openjpa.jdbc.DBDictionary: oracle(DriverVendor=oracle92)>
####<25.03.2011 19:09:44 YEKT> <Info> <Security> <vpc> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1301062184058> <BEA-090511> <The following exception has occurred:

Comments

Ivica Arsov

Hi,

I didn't understand your process, but anyway why don't you just open the standby database in read only mode (active data guard) ?

Anar Godjaev

hi,

You use active DataGuard? Secondary Database (Standby database) in read only mode?

Can you please paste here: (Standby Database)

SQL>select open_mode from v$database;

And

SQL> set linesize 1000

SQL> set pagesize 100

SQL>

SQL> select name, value from v$dataguard_Stats;

Thank you

saurabh

you database version information is important.

yes you can do this. some important points to remeber.

1. before shutdown of the dr defer the log_archive_dest for standby to stop archive shipping to the standby.

2. after shuttting down the DR copy the datafile and controlfile as well.

3. After your testing is completed.

4. REMANE  PROD_bak to PROD and then start the standby dataabse. The database which you have open if not required then delete all the file before renaming.


mrmessin

You can open a standby database read only, no issues there keep in mind that archive log apply will stop while the database is read only unless you use the active dataguard option, but depending on version of the database it may not be available.

See Oracle documentation I got all this from there:

http://docs.oracle.com/cd/B10501_01/server.920/a96653/manage_ps.htm


To open a standby database for read-only access when it is currently shut down:

  1. Start the Oracle instance for the standby database without mounting it:

          SQL> STARTUP NOMOUNT;

  1. Mount the standby database:

          SQL> ALTER DATABASE MOUNT STANDBY DATABASE;

  1. Open the database for read-only access:

          SQL> ALTER DATABASE OPEN READ ONLY;

To open a standby database for read-only access when it is currently performing managed recovery:

     Cancel log apply services:

          SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;

     Open the database for read-only access:

          SQL> ALTER DATABASE OPEN READ ONLY;

Now to put the database back to physical standby and apply the logs

To change the standby database from being open for read-only access to performing managed recovery:

     Terminate all active user sessions on the standby database, a shutdown works very well here

          SQL> shutdown immediate;

     Restart log apply services:

          SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;

Anar Godjaev

HI again,

Please check step by step in Secondary (Standby Database)

SQL> set linesize 1000

SQL> set pagesize 100

SQL>

SQL> select name, value from v$dataguard_Stats;  -- is ok then check below step:

For example: in Standby database:

NAME                      VALUE

------------------------- --------------------------------------------------

transport lag             +00 00:00:00

apply lag                 +00 00:00:00

apply finish time         +00 00:00:00.000

estimated startup time    21

------------------------------------------------------------------------------

Next Step in Secondary database:

          SQL> STARTUP NOMOUNT;

          SQL> ALTER DATABASE MOUNT STANDBY DATABASE;

          SQL> ALTER DATABASE OPEN READ ONLY;

And starying again MRP process in Secondary database:

STARTUP NOMOUNT

ALTER DATABASE MOUNT STANDBY DATABASE;

ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT FROM SESSION;

Thank you

unknown-1052419

Thanks ALL,

DB 11.2.0.1

Supposing I will not hold-off or disrupt the standby db process since I am afraid that disaster strikes while it is paused off.

But instead I will create another reporting db  out of the standby because the standby server has not so much load on it.

Is this possible with RMAN? Creating a duplicate db out of the standby?

saratpvv

Why not - You can create duplicate db - Till now you haven't posted your db version..?

unknown-1052419

My db is 11.2.0.1

saurabh

As your database is of 11g version. You can take advantage of snapshot standby.

unknown-1052419

I searched google about snapshot db but it so complicated.

It says I need to configure DGBROKER which also complicated by its name.

Can I create snapshot db without using dgbroker?

Thanks,

saurabh
Answer
Marked as Answer by unknown-1052419 · Sep 27 2020
unknown-1052419

Thanks Saur

1 - 12
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Apr 29 2011
Added on Mar 25 2011
5 comments
2,277 views