Oracle Database startup issue

[Former Member]

Hi

I am middel on upgrade SAP BW from 7.0 to 7.3. After shadow instance was create the disp+work it sto...

SQL> startup
ORA-24324: service handle not initialized
ORA-01041: internal error. hostdef extension doesn't exist
SQL> shutdown immediate
ORA-24324: service handle not initialized
ORA-01041: internal error. hostdef extension doesn't exist
SQL> show parameter;
ERROR:
ORA-03114: not connected to ORACLE

SQL>

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

C:\app\Administrator\product\11.2.0\dbhome_1\BIN>Lsnrctl start

LSNRCTL for 64-bit Windows: Version 11.2.0.3.0 - Production on 15-OCT-2012 14:42
:50

Copyright (c) 1991, 2011, Oracle.  All rights reserved.

TNS-01106: Listener using listener name LISTENER has already been started

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

C:\app\Administrator\product\11.2.0\dbhome_1\BIN>Lsnrctl status

LSNRCTL for 64-bit Windows: Version 11.2.0.3.0 - Production on 15-OCT-2012 14:43
:26

Copyright (c) 1991, 2011, Oracle.  All rights reserved.

Connecting to (ADDRESS=(PROTOCOL=IPC)(KEY=BW1.WORLD))
STATUS of the LISTENER
------------------------
Alias                     LISTENER
Version                   TNSLSNR for 64-bit Windows: Version 11.2.0.3.0 - Produ
ction
Start Date                15-OCT-2012 13:32:59
Uptime                    0 days 1 hr. 10 min. 27 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   C:\app\Administrator\product\11.2.0\dbhome_1\network\a
dmin\listener.ora
Listener Log File         C:\app\Administrator\diag\tnslsnr\BWMNT10\listener\ale
rt\log.xml
Listening Endpoints Summary...
  (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\BW1.WORLDipc)))
  (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\BW1ipc)))
  (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=BWMNT10)(PORT=1527)))
Services Summary...
Service "BW1" has 1 instance(s).
  Instance "BW1", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully

C:\app\Administrator\product\11.2.0\dbhome_1\BIN>

Any idea for this problem.

Thanks

[stefan_koehler · Accepted solution]

Hi Ejersbo,

this has nothing to do with patches or memory. Your local server time does not match the domain server time and as a result the authentication failed.

Just sync your server time with the DC and it will work again.

http://blogs.msdn.com/b/sanket/archive/2006/11/02/synchronizing-machine-time-with-domain-controller....

Regards

Stefan

[Former Member · Accepted solution]

Hi Stefan,

I did  Synchronizing machine time with domain controller but I have stil the same problem, My problem start during sap BW upgrade after Shadow instance cretet.

Thanks

[stefan_koehler · Accepted solution]

Hi Ejersbo,

have you closed your previous SQL*Plus session and restarted the instance afterwards?  If not please proceed as the following:

*** New SQL*Plus session ***
SQL> shutdown abort;
SQL> startup

If the issue still persists - please zip the alert.log file and attach it here.

Just out of curiosity. What's that for an ORACLE_HOME path "C:\app\Administrator\product\11.2.0\dbhome_1\"? That does not look like a SAP installation. Maybe there is something wrong with your environment as well.

Regards

Stefan

[Former Member · Accepted solution]

Hi Stefan,

I have closed sql*plus session as you mention,

My ORACLE_HOME path is C:\app\Administrator\product\11.2.0\dbhome_1

Thanks

[Former Member · Accepted solution]

Hi,

I have this log file:

Trace file C:\ORACLE\BW1\SAPTRACE\diag\rdbms\bw1\bw1\trace\bw1_arc0_1648.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Windows NT Version V6.1 Service Pack 1
CPU                 : 4 - type 8664, 4 Physical Cores
Process Affinity    : 0x0x0000000000000000
Memory (Avail/Total): Ph:6347M/8191M, Ph+PgF:33452M/36861M
VM name             : VMWare Version (6)
Instance name: bw1
Redo thread mounted by this instance: 1
Oracle process number: 17
Windows thread id: 1648, image: ORACLE.EXE (ARC0)

*** 2012-10-15 12:35:13.675
*** SESSION ID:(44.3) 2012-10-15 12:35:13.675
*** CLIENT ID:() 2012-10-15 12:35:13.675
*** SERVICE NAME:() 2012-10-15 12:35:13.675
*** MODULE NAME:() 2012-10-15 12:35:13.675
*** ACTION NAME:() 2012-10-15 12:35:13.675

Initial buffer sizes: read 1024K, overflow 832K, change 805K

*** 2012-10-15 12:35:14.737
ORA-19815: WARNING: db_recovery_file_dest_size of 31457280000 bytes is 100.00% used, and has 0 remaining bytes available.
************************************************************************
You have following choices to free up space from recovery area:
1. Consider changing RMAN RETENTION POLICY. If you are using Data Guard,
   then consider changing RMAN ARCHIVELOG DELETION POLICY.
2. Back up files to tertiary device such as tape using RMAN
   BACKUP RECOVERY AREA command.
3. Add disk space and increase db_recovery_file_dest_size parameter to
   reflect the new space.
4. Delete unnecessary files using RMAN DELETE command. If an operating
   system command was used to delete files, then use RMAN CROSSCHECK and
   DELETE EXPIRED commands.
************************************************************************
*** 2012-10-15 12:35:14.737 4320 krsh.c
ARC0: Error 19809 Creating archive log file to 'E:\ORACLE\BW1\ORAFLASH\BW1\ARCHIVELOG\2012_10_15\O1_MF_1_1824_%U_.ARC'
*** 2012-10-15 12:35:14.737 2932 krsi.c
krsi_dst_fail: dest:1 err:19809 force:0 blast:1
DDE: Problem Key 'ORA 312' was flood controlled (0x1) (no incident)
ORA-00312: online log 4 thread 1: 'E:\ORACLE\BW1\MIRRLOGB\LOG_G14M2.DBF'
DDE: Problem Key 'ORA 312' was flood controlled (0x1) (no incident)
ORA-00312: online log 4 thread 1: 'C:\ORACLE\BW1\ORIGLOGB\LOG_G14M1.DBF'
ORA-00312: online log 4 thread 1: 'E:\ORACLE\BW1\MIRRLOGB\LOG_G14M2.DBF'
*** 2012-10-15 12:35:14.769 4481 kcrr.c

I did tried to  increase db_recovery_file_dest_size parameter with but:

SQL> ALTER SYSTEM SET DB_RECOVERY_FILE_DEST_SIZE = 8G COPE=BOTH SID='*';

ALTER SYSTEM SET DB_RECOVERY_FILE_DEST_SIZE = 8G COPE=BOTH SID='*'

*

ERROR at line 1:

ORA-01034: ORACLE not available

Process ID: 0

Session ID: 0 Serial number: 0

Any idea?

Thanks

[Former Member · Accepted solution]

Hi,

Please check the below points.

1. Check archive log drive is full or not ...or  any other dirve is full ..?...If full please move older logs to other location.
2. Please the share the latest log file "alert_BW1.log"   probably on the location 

C:\ORACLE\BW1\SAPTRACE\diag\rdbms\bw1\bw1\trace\alert_BW1.log

Regards

Sahil

[Former Member · Accepted solution]

Hi Sahil,

I did move older archive log on other location but no help;

The alert_BW1.log file i more than 1 gb. Her is the last part of that:

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

ARCH: Error 19809 Creating archive log file to 'E:\ORACLE\BW1\ORAFLASH\BW1\ARCHIVELOG\2012_10_15\O1_MF_1_1824_%U_.ARC'

Errors in file C:\ORACLE\BW1\SAPTRACE\diag\rdbms\bw1\bw1\trace\bw1_ora_3208.trc:

ORA-16038: log 4 sequence# 1824 cannot be archived

ORA-19809: limit exceeded for recovery files

ORA-00312: online log 4 thread 1: 'C:\ORACLE\BW1\ORIGLOGB\LOG_G14M1.DBF'

ORA-00312: online log 4 thread 1: 'E:\ORACLE\BW1\MIRRLOGB\LOG_G14M2.DBF'

USER (ospid: 3208): terminating the instance due to error 16038

System state dump requested by (instance=1, osid=3208), summary=[abnormal instance termination].

System State dumped to trace file C:\ORACLE\BW1\SAPTRACE\diag\rdbms\bw1\bw1\trace\bw1_diag_3204.trc

ARC0: STARTING ARCH PROCESSES

Logins disabled; aborting ARCH process startup (1092)

ARC0: Archival disabled due to shutdown: 1092

Shutting down archive processes

Archiving is disabled

Dumping diagnostic data in directory=[cdmp_20121015230201], requested by (instance=1, osid=3208), summary=[abnormal instance termination].

Instance terminated by USER, pid = 3208

Tue Oct 16 08:20:54 2012

Starting ORACLE instance (normal)

LICENSE_MAX_SESSION = 0

LICENSE_SESSIONS_WARNING = 0

Picked latch-free SCN scheme 3

Using LOG_ARCHIVE_DEST_1 parameter default value as USE_DB_RECOVERY_FILE_DEST

Autotune of undo retention is turned on.

LICENSE_MAX_USERS = 0

SYS auditing is disabled

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.

Windows NT Version V6.1 Service Pack 1

CPU                 : 4 - type 8664, 4 Physical Cores

Process Affinity    : 0x0x0000000000000000

Memory (Avail/Total): Ph:2780M/8191M, Ph+PgF:29773M/36861M

VM name             : VMWare Version (6)

Using parameter settings in server-side spfile C:\APP\ADMINISTRATOR\PRODUCT\11.2.0\DBHOME_1\DATABASE\SPFILEBW1.ORA

System parameters with non-default values:

  processes                = 80

  sessions                 = 160

  shared_pool_size         = 624M

  shared_pool_reserved_size= 64424509

  filesystemio_options     = "setall"

  control_files            = "C:\ORACLE\BW1\ORIGLOGA\CNTRL\CNTRLBW1.DBF"

  control_files            = "C:\ORACLE\BW1\ORIGLOGB\CNTRL\CNTRLBW1.DBF"

  control_files            = "C:\ORACLE\BW1\SAPDATA1\CNTRL\CNTRLBW1.DBF"

  control_file_record_keep_time= 30

  db_block_size            = 8192

  db_cache_size            = 624M

  compatible               = "11.2.0"

  log_archive_format       = "%t_%s_%r.dbf"

  log_buffer               = 4096000

  db_recovery_file_dest    = "E:\oracle\BW1\oraflash"

  db_recovery_file_dest_size= 30000M

  log_checkpoints_to_alert = TRUE

  dml_locks                = 4000

  replication_dependency_tracking= FALSE

  undo_tablespace          = "PSAPUNDO"

  _in_memory_undo          = FALSE

  recyclebin               = "off"

  remote_os_authent        = TRUE

  remote_login_passwordfile= "EXCLUSIVE"

  parallel_execution_message_size= 16384

  _table_lookup_prefetch_size= 0

  audit_file_dest          = "C:\ORACLE\BW1\SAPTRACE\AUDIT"

  db_name                  = "BW1"

  open_cursors             = 2000

  _sort_elimination_cost_ratio= 10

  _b_tree_bitmap_plans     = FALSE

  star_transformation_enabled= "true"

  parallel_threads_per_cpu = 1

  query_rewrite_enabled    = "false"

  _index_join_enabled      = FALSE

  _optim_peek_user_binds   = FALSE

  pga_aggregate_target     = 600M

  _optimizer_mjc_enabled   = FALSE

  diagnostic_dest          = "C:\ORACLE\BW1\SAPTRACE"

  max_dump_file_size       = "20000"

Deprecated system parameters with specified values:

  remote_os_authent       

End of deprecated system parameter listing

Tue Oct 16 08:20:54 2012

PMON started with pid=2, OS id=6112

Tue Oct 16 08:20:54 2012

PSP0 started with pid=3, OS id=4416

Tue Oct 16 08:20:55 2012

VKTM started with pid=4, OS id=2584 at elevated priority

VKTM running at (10)millisec precision with DBRM quantum (100)ms

Tue Oct 16 08:20:55 2012

GEN0 started with pid=5, OS id=6116

Tue Oct 16 08:20:55 2012

DIAG started with pid=6, OS id=4548

Tue Oct 16 08:20:55 2012

DBRM started with pid=7, OS id=2336

Tue Oct 16 08:20:55 2012

DIA0 started with pid=8, OS id=5588

Tue Oct 16 08:20:55 2012

MMAN started with pid=9, OS id=4812

Tue Oct 16 08:20:55 2012

DBW0 started with pid=10, OS id=5196

Tue Oct 16 08:20:55 2012

LGWR started with pid=11, OS id=5204

Tue Oct 16 08:20:55 2012

CKPT started with pid=12, OS id=4920

Tue Oct 16 08:20:55 2012

SMON started with pid=13, OS id=4224

Tue Oct 16 08:20:55 2012

RECO started with pid=14, OS id=5536

Tue Oct 16 08:20:55 2012

MMON started with pid=15, OS id=5016

Tue Oct 16 08:20:55 2012

MMNL started with pid=16, OS id=3580

ORACLE_BASE from environment = C:\app\Administrator

Tue Oct 16 08:20:56 2012

ALTER DATABASE   MOUNT

Successful mount of redo thread 1, with mount id 446073256

Database mounted in Exclusive Mode

Lost write protection disabled

Completed: ALTER DATABASE   MOUNT

Tue Oct 16 08:21:00 2012

ALTER DATABASE OPEN

LGWR: STARTING ARCH PROCESSES

Tue Oct 16 08:21:00 2012

ARC0 started with pid=18, OS id=5632

ARC0: Archival started

LGWR: STARTING ARCH PROCESSES COMPLETE

Errors in file C:\ORACLE\BW1\SAPTRACE\diag\rdbms\bw1\bw1\trace\bw1_ora_4496.trc:

ORA-19815: WARNING: db_recovery_file_dest_size of 31457280000 bytes is 100.00% used, and has 0 remaining bytes available.

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

You have following choices to free up space from recovery area:

1. Consider changing RMAN RETENTION POLICY. If you are using Data Guard,

   then consider changing RMAN ARCHIVELOG DELETION POLICY.

2. Back up files to tertiary device such as tape using RMAN

   BACKUP RECOVERY AREA command.

3. Add disk space and increase db_recovery_file_dest_size parameter to

   reflect the new space.

4. Delete unnecessary files using RMAN DELETE command. If an operating

   system command was used to delete files, then use RMAN CROSSCHECK and

   DELETE EXPIRED commands.

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

ARCH: Error 19809 Creating archive log file to 'E:\ORACLE\BW1\ORAFLASH\BW1\ARCHIVELOG\2012_10_16\O1_MF_1_1824_%U_.ARC'

Errors in file C:\ORACLE\BW1\SAPTRACE\diag\rdbms\bw1\bw1\trace\bw1_ora_4496.trc:

ORA-16038: log 4 sequence# 1824 cannot be archived

ORA-19809: limit exceeded for recovery files

ORA-00312: online log 4 thread 1: 'C:\ORACLE\BW1\ORIGLOGB\LOG_G14M1.DBF'

ORA-00312: online log 4 thread 1: 'E:\ORACLE\BW1\MIRRLOGB\LOG_G14M2.DBF'

System state dump requested by (instance=1, osid=4496), summary=[abnormal instance termination].

System State dumped to trace file C:\ORACLE\BW1\SAPTRACE\diag\rdbms\bw1\bw1\trace\bw1_diag_4548.trc

USER (ospid: 4496): terminating the instance due to error 16038

Dumping diagnostic data in directory=[cdmp_20121016082101], requested by (instance=1, osid=4496), summary=[abnormal instance termination].

ARC0: STARTING ARCH PROCESSES

Logins disabled; aborting ARCH process startup (1092)

ARC0: Archival disabled due to shutdown: 1092

Shutting down archive processes

Archiving is disabled

Instance terminated by USER, pid = 4496

Thanks

[Former Member · Accepted solution]

You received ORA-19815 and ORA-19809 errors. The limit for recovery files specified by the DB_RECOVERY_FILE_DEST_SIZE was exceeded.

Action: There are five possible solutions:

          1) Take frequent backup of recovery area using RMAN.

          2) Consider changing RMAN retention policy.

          3) Consider changing RMAN archived log deletion policy.

          4) Add disk space and increase DB_RECOVERY_FILE_DEST_SIZE.

          5) Delete files from recovery area using RMAN.

Regards

Roman

[Former Member · Accepted solution]

Could you upload the file "C:\ORACLE\BW1\SAPTRACE\diag\rdbms\bw1\bw1\trace\bw1_diag_4548.trc"?

>> ORA-19815: WARNING: db_recovery_file_dest_size of 31457280000 bytes is 100.00% used, and has 0 remaining bytes available.

Additionally, it looks like the archive log destination is still full. Could you double check the freespace?

Best regards,

Orkun Gedik

[Former Member · Accepted solution]

I did tried to  increase db_recovery_file_dest_size parameter with but:

I can not connect to Oracle I get this error:

SQL> ALTER SYSTEM SET DB_RECOVERY_FILE_DEST_SIZE = 8G COPE=BOTH SID='*';

ALTER SYSTEM SET DB_RECOVERY_FILE_DEST_SIZE = 8G COPE=BOTH SID='*'

*

ERROR at line 1:

ORA-01034: ORACLE not available

Process ID: 0

Session ID: 0 Serial number: 0

Thanks

[Former Member · Accepted solution]

Hello,

Archive log dest is still full.Run the below command to increase the quota limit.(It will be only helpful if space available on the disk.)

Please run the below command when DB in mount mode.

to check DB mount mode .  #  Select open_mode from v$database;

ALTER SYSTEM SET DB_RECOVERY_FILE_DEST_SIZE = 10G SCOPE=BOTH;

Regards,

Sahil

Message was edited by: Sahil Garg

[former_member191911 · Accepted solution]

You should execute a startup nomount first and then execute the command.

Kr. Mark

[Former Member · Accepted solution]

Hello,

The command you were using it was having syntax issue also.

Have u tried with the comamnd that i have provided.

if that is not working do one thing.

go to $Oracle_Home/database folder.

open initBW1.ora and change  the value of parameter

DB_RECOVERY_FILE_DEST_SIZE=10G.

after that follow below steps.

1. shutdown immediate.

2. startup pfile='path of pfile'   ## example (  startup pfile='d:\oracle\1120\database\initBW1.ora')

Regards,

Sahil

[Former Member · Accepted solution]

Her is log file bw1_diag_4548 added as zip file:

bw1_diag_4548.zip.txt.zip

[Former Member · Accepted solution]

>> ALTER SYSTEM SET DB_RECOVERY_FILE_DEST_SIZE = 10G SCOPE=BOTH;

It is not good to modify the parameter, if there's not enough freespace on the storage.

On the other could you execute the steps, below;

RMAN> CONNECT TARGET /

RMAN> CROSSCHECK ARCHIVELOG ALL;

RMAN> DELETE EXPIRED ARCHIVELOG ALL;

Best regards,

Orkun Gedik

[Former Member · Accepted solution]

Hi,

I did change parameter DB_RECOVERY_FILE_DEST_SIZE to 10G. And restart server, but I have still the same problem, When I tried :

SQL> ALTER SYSTEM SET DB_RECOVERY_FILE_DEST_SIZE = 10G SCOPE=BOTH;
ERROR:
ORA-03114: not connected to ORACLE

SQL>

Thanks

[Former Member · Accepted solution]

>> Additionally, it looks like the archive log destination is still full. Could you double check the freespace?

Did you check the freespace?

[Former Member · Accepted solution]

Hi,

When I run connecet I have this :

RMAN> CONNECET TARGET/

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "identifier": expecting one of: "advise, allocat
e, alter, backup, @, catalog, change, configure, connect, convert, copy, create,
crosscheck, delete, drop, duplicate, exit, flashback, grant, host, import, list
, mount, open, print, quit, recover, register, release, repair, replace, report,
reset, restore, resync, revoke, run, send, set, show, shutdown, spool, sql, sta
rtup, switch, transport, unregister, upgrade, validate, {, "
RMAN-01008: the bad identifier was: CONNECET
RMAN-01007: at line 1 column 1 file: standard input

RMAN>

Thanks

[Former Member · Accepted solution]

You typed CONNECET. Please be careful when you are typing the commands

[Former Member · Accepted solution]

CONNECT TARGET /

[Former Member · Accepted solution]

When I check: E:\oracle\BW1\oraflash\BW1\ARCHIVELOG\2012_10_16 ther is not thing there I did move alle file on other place.

Thanks

[Former Member · Accepted solution]

Her is :

RMAN> CONNECT TARGET /

connected to target database (not started)

RMAN>

Thanks

[Former Member · Accepted solution]

Her is :

RMAN> CONNECT TARGET/

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-06167: already connected

RMAN> CROSSCHECK ARCHIVELOG ALL;

using target database control file instead of recovery catalog
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of crosscheck command at 10/16/2012 10:07:15
RMAN-12010: automatic channel allocation initialization failed
RMAN-06403: could not obtain a fully authorized session
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist

RMAN> DELETE EXPIRED ARCHIVELOG ALL;

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of delete command at 10/16/2012 10:07:34
RMAN-06403: could not obtain a fully authorized session
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist

RMAN>

thanks

[Former Member · Accepted solution]

RMAN> CONNECT TARGET /

RMAN> STARTUP MOUNT;

RMAN> CROSSCHECK ARCHIVELOG ALL;

RMAN> DELETE EXPIRED ARCHIVELOG ALL;

[Former Member · Accepted solution]

Please provide output of

RMAN> report obsolete;

Regards

Roman

[Former Member · Accepted solution]

Thanks Orkun,

Thats help, Now I will run this :

SQL> ALTER SYSTEM SET DB_RECOVERY_FILE_DEST_SIZE = 10G SCOPE=BOTH;

Thanks

[Former Member · Accepted solution]

Ok. If you have enough storage, no problem

[Former Member · Accepted solution]

Yes Now I can start sap and I can continue with upgrade.

Thanks to you and alle of you for help.

[Former Member · Accepted solution]

Good to hear this good luck

[Former Member]

I will try to cleanup the memory segments manually,

And no I  didnot ran the utlrp.sql etc. scripts after the upgrade . Can I run it now middel on my upgrdae?

Thanks

[former_member191911]

Well, I missed one question.. 🙂 Did you upgraded/patched Oracle as part of the SAP upgrade?

If so, you should make sure that these kind of scripts (mentioned in the upgrade guide) are executed correctly.

Sorry for the confusion.

Kind regards,

Mark

[Former Member]

Well I did  mis undrestand your question, I am upgradeing sap installation and not Oracle,

and I did rester server but it did not help,

Thanks

[Former Member]

After restet I did tried to start Oracle:

C:\Users\Administrator>sqlplus / as sysdba

SQL*Plus: Release 11.2.0.3.0 Production on Mon Oct 15 16:58:20 2012

Copyright (c) 1982, 2011, Oracle.  All rights reserved.

Connected to an idle instance.

SQL> startup
ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance
ORACLE instance started.

Total System Global Area 1352953856 bytes
Fixed Size                  2254984 bytes
Variable Size             687867768 bytes
Database Buffers          654311424 bytes
Redo Buffers                8519680 bytes
Database mounted.
ORA-03113: end-of-file on communication channel
Process ID: 3772
Session ID: 44 Serial number: 3

SQL> shutdown immediate
ORA-24324: service handle not initialized
ORA-01041: internal error. hostdef extension doesn't exist
SQL>

Thanks

[Former Member]

Could you check the database alert log and usertrace logs and upload here please?

[former_member191911]

Could be that some shared memory segments are "corrupted".

Can you stop all Oracle processes, cleanup the memory segments used by Oracle (since it's Windows, probably a reboot of the server) and start the database again?

Kind regards,

Mark

[Former Member]

Hello Mark,

Can you guide me, how can I  cleanup the memory segments.

Thanks.

[former_member191911]

Good question!

I'm not really Windows minded, but I know from experience that in many cases a reboot of the system is the only way to be sure that memory is cleaned up correctly.

One other option could be to stop the Oracle and SAP processes and check in the task manager if there are still processes active. These should be manually canceled.

One other question; did you ran the utlrp.sql etc. scripts after the upgrade?

Kind regards,

Mark

[Former Member]

Hi Reza,

Check the document, below;

Note 328822 - AIX kernel extension for Oracle

Best regards,

Orkun Gedik

[Former Member]

Hi Orkun,

My Oracle run on Windows and not AIX. And I have this problem on middel of upgrade after the shadow instance was createt.

Thanks

[Former Member]

Sorry, I couldn't see the system running on Windows. Ok, did you applied the latest db patches? When did you faced with this error? Was the database able to started, successfully before the upgrade?

Additionally, could you check the alert log?

[Former Member]

Thanks for reply.

No I did not applied the latest db patches. I faced this problem middel on Upgrdae on Pre-processing.  I did used this note  1734716 - ORA-01034: Oracle not available , but did not help.

Thanks

[Former Member]

Hi,

Let's move step by step. Startup the database and get the error. Then, try to shutdown the database and get the second error. So, startup the database again and execute the statement below.

SQL> show parameter background_dump_dest

Then, goto the path referred by the statement and upload "alert_<SID>.log". If it is large to upload, you can zip it.

SQL> show parameter user_dump_dest

Then, goto the path referred by the statement and upload latest .trc file.

Best regards,

Orkun Gedik