Results 1 to 9 of 9
  1. #1
    Join Date
    Sep 2003
    Location
    pakistan
    Posts
    3

    Unanswered: shred memory realm does not exist

    Hi,
    I have installed Oracle 9i on Windows 2000 Advanced server. The installation was fine. Didnt get any errors, but when I restarted the server my database doesnt start automatically.
    When I try to log in using a user I get the following message:

    Oracle not available
    Shared memory realm does not exist

    Then I have to connect by sys and manually start the database. Then everything works fine.

    I have check my ORACLE_SID in registry, its properly set. All the services are started. I created the service again using oradim but didnt correct my problem.
    I need to have my database started automatically after server restart.

    I check alert log. Following is an extract from alert file.

    Sun Jun 29 04:11:45 2003
    Error 1534 happened during db open, shutting down database
    USER: terminating instance due to error 1534
    Instance terminated by USER, pid = 408
    ORA-1092 signalled during: ALTER DATABASE OPEN...
    Sun Jun 29 04:12:28 2003
    Starting ORACLE instance (normal)
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    SCN scheme 2
    Using log_archive_dest parameter default value
    LICENSE_MAX_USERS = 0
    SYS auditing is disabled
    Starting up ORACLE RDBMS Version: 9.2.0.1.0.
    System parameters with non-default values:
    processes = 150
    timed_statistics = TRUE
    shared_pool_size = 159383552
    sga_max_size = 742989784
    large_pool_size = 58720256
    java_pool_size = 33554432
    nls_date_format = DD\MM\YYYY
    control_files = E:\oracle\oradata\LALPIR\CONTROL01.CTL, E:\oracle\oradata\LALPIR\CONTROL02.CTL, F:\oracle\oradata\LALPIR\CONTROL03.CTL
    db_block_size = 8192
    db_writer_processes = 1
    db_cache_size = 209715200
    compatible = 9.2.0.0.0
    log_archive_dest_1 =
    log_archive_dest_2 =
    log_buffer = 104857600
    log_checkpoint_interval = 100
    log_checkpoint_timeout = 0
    db_file_multiblock_read_count= 8
    fast_start_mttr_target = 300
    rollback_segments = RBS, RBS01, RBS02, RBS03, RBS04, RBS05, RBS06, RBS07, RBS08, RBS09, RBS10
    undo_management = MANUAL
    undo_retention = 600
    remote_login_passwordfile= EXCLUSIVE
    db_domain =
    instance_name = LALPIR
    dispatchers = (PROTOCOL=TCP) (SERVICE=LALPIRXDB)
    job_queue_processes = 10
    hash_join_enabled = TRUE
    background_dump_dest = E:\oracle\admin\LALPIR\bdump
    user_dump_dest = E:\oracle\admin\LALPIR\udump
    core_dump_dest = E:\oracle\admin\LALPIR\cdump
    sort_area_size = 524288
    db_name = LALPIR
    open_cursors = 300
    star_transformation_enabled= FALSE
    query_rewrite_enabled = FALSE
    pga_aggregate_target = 25165824
    aq_tm_processes = 1
    PMON started with pid=2
    DBW0 started with pid=3
    LGWR started with pid=4
    CKPT started with pid=5
    SMON started with pid=6
    RECO started with pid=7
    CJQ0 started with pid=8
    QMN0 started with pid=9
    Sun Jun 29 04:12:32 2003
    starting up 1 shared server(s) ...
    starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
    Sun Jun 29 04:12:32 2003
    ALTER DATABASE MOUNT
    Sun Jun 29 04:12:37 2003
    Successful mount of redo thread 1, with mount id 2998935472.
    Sun Jun 29 04:12:37 2003
    Database mounted in Exclusive Mode.
    Completed: ALTER DATABASE MOUNT
    Sun Jun 29 04:12:37 2003
    ALTER DATABASE OPEN
    Sun Jun 29 04:12:37 2003
    Beginning crash recovery of 1 threads
    Sun Jun 29 04:12:37 2003
    Started first pass scan
    Sun Jun 29 04:12:38 2003
    Completed first pass scan
    38 redo blocks read, 5 data blocks need recovery
    Sun Jun 29 04:12:38 2003
    Started recovery at
    Thread 1: logseq 4, block 762, scn 0.213358314
    Recovery of Online Redo Log: Thread 1 Group 4 Seq 4 Reading mem 0
    Mem# 0 errs 0: F:\ORACLE\ORADATA\LALPIR\REDO04.LOG
    Sun Jun 29 04:12:38 2003
    Ended recovery at
    Thread 1: logseq 4, block 800, scn 0.213378350
    5 data blocks read, 5 data blocks written, 38 redo blocks read
    Crash recovery completed successfully
    Sun Jun 29 04:12:39 2003
    Thread 1 advanced to log sequence 5
    Thread 1 opened at log sequence 5
    Current log# 5 seq# 5 mem# 0: F:\ORACLE\ORADATA\LALPIR\REDO05.LOG
    Successful open of redo thread 1.
    Sun Jun 29 04:12:40 2003
    LOG_CHECKPOINT_INTERVAL was set when MTTR advisory was switched on.
    Sun Jun 29 04:12:40 2003
    SMON: enabling cache recovery
    SMON: enabling tx recovery
    Sun Jun 29 04:12:44 2003
    Database Characterset is WE8MSWIN1252
    replication_dependency_tracking turned off (no async multimaster replication found)
    Completed: ALTER DATABASE OPEN
    Sun Jun 29 04:14:05 2003
    Shutting down instance: further logons disabled
    Shutting down instance (immediate)
    License high water mark = 6
    Waiting for dispatcher 'D000' to shutdown
    All dispatchers and shared servers shutdown
    Sun Jun 29 04:14:06 2003
    ALTER DATABASE CLOSE NORMAL
    Sun Jun 29 04:14:06 2003
    SMON: disabling tx recovery
    SMON: disabling cache recovery
    Sun Jun 29 04:14:07 2003
    Shutting down archive processes
    Archiving is disabled
    Archive process shutdown avoided: 0 active
    Thread 1 closed at log sequence 5
    Successful close of redo thread 1.
    Sun Jun 29 04:14:07 2003
    Completed: ALTER DATABASE CLOSE NORMAL
    Sun Jun 29 04:14:07 2003
    ALTER DATABASE DISMOUNT
    Completed: ALTER DATABASE DISMOUNT
    ARCH: Archiving is disabled
    Shutting down archive processes
    Archiving is disabled
    Archive process shutdown avoided: 0 active
    ARCH: Archiving is disabled
    Shutting down archive processes
    Archiving is disabled
    Archive process shutdown avoided: 0 active

    Can anyone help me out with this.

  2. #2
    Join Date
    Sep 2003
    Location
    china
    Posts
    3
    pls start your listener before start instance
    Last edited by Hai Wang; 09-20-03 at 13:02.

  3. #3
    Join Date
    Aug 2003
    Posts
    1
    Hi,

    If you are using P-4 machine, then I guess you will manually have to turn on the database everytime time you turn on your server. I'm using Oracle 8i on a P4 machine and go through the same hassle everyday.

    bye


    Hassan

  4. #4
    Join Date
    Nov 2002
    Location
    Desk, slightly south of keyboard
    Posts
    697
    Hi,

    An invalid init.ora can cause this on Win2K when autostarting via the service manager. If this is the case it will fail to start properly every time. If so, start the instance via SVRMGRL and see what error it's reporting.

    If it starts fine sometimes, but not others (particularly following an install and reboot) it's a Win2K problem, something to do with M$ changing the way the services get started up. Some machines are problematic, some aren't (and it doesn't appear related to CPU type - just Win2K). Google for the error number, different people have found different solutions for their instances.

    Hth
    Bill

  5. #5
    Join Date
    Sep 2003
    Location
    The Netherlands
    Posts
    311
    Hi,

    ther alert.log signals an 1534 error. Assuming this is an ORA-1534, it means that a specified rollback segment in the used init.ora at automatic startup does not exist in the database.
    So when the database is up and running check the rollback segments the way they are mentioned in the init.ora. The alert.log shows :

    rollback_segments = RBS, RBS01, RBS02, RBS03, RBS04, RBS05, RBS06, RBS07, RBS08, RBS09, RBS10

    is this correct and are they all present in the database?
    Is the right init.ora used or are there more init.ora's that can be used (for example in the ORACLE_HOME\Dbs directory)?
    Do you get the same errror using the simple statement 'STARTUP' in svrmgrl or do you use the parameter for the location of the init.ora ?

    Good luck.

    Edwin

  6. #6
    Join Date
    Sep 2003
    Posts
    1

    shred memory realm does not exist

    I am getting same issue with 9ias installation on SuSE linux 8.1. I have already set my shmmax to 374meg - which a half of total physical RAM.

    Any idea how to resolve this.

    - Olu

  7. #7
    Join Date
    Sep 2003
    Location
    pakistan
    Posts
    3
    Originally posted by Hai Wang
    pls start your listener before start instance
    my listener is already started. i cheked TNSListener service. Its set to auto start and it is running when the machine reboots.

  8. #8
    Join Date
    Sep 2003
    Location
    pakistan
    Posts
    3
    Originally posted by evanhattem
    Hi,

    ther alert.log signals an 1534 error. Assuming this is an ORA-1534, it means that a specified rollback segment in the used init.ora at automatic startup does not exist in the database.
    So when the database is up and running check the rollback segments the way they are mentioned in the init.ora. The alert.log shows :

    rollback_segments = RBS, RBS01, RBS02, RBS03, RBS04, RBS05, RBS06, RBS07, RBS08, RBS09, RBS10

    is this correct and are they all present in the database?
    Is the right init.ora used or are there more init.ora's that can be used (for example in the ORACLE_HOME\Dbs directory)?
    Do you get the same errror using the simple statement 'STARTUP' in svrmgrl or do you use the parameter for the location of the init.ora ?

    Good luck.

    Edwin

    hi,
    i checked all my rollback segments. all of them exist. when i connect using sqlplus. i get this message:

    connected to an idle instance

    then i have to issue the startup command to have my database started.
    i have prepared a couple of servers the same way as it is our requirements. same machine, same OS, same everything. i'm only having this problem with one database.

  9. #9
    Join Date
    Sep 2003
    Location
    The Netherlands
    Posts
    311
    Hi,

    Are you positive that the right init.ora is used ?

    A workaround maybe the following.

    Change the startup property for the instance from automatic to manual.

    Create a START_DB.CMD file on the filesystem containing the following text :

    set ORACLE_SID=instance_name

    sqlplus /nolog @startup.sql

    then create a file called startup.sql containing the follwing text:
    connect sys/sys_pwd
    startup
    exit

    If needed you can add the complete path before the name of the startup file.

    Next, add the START_DB.CMD to the startmenu option 'STARTUP'. This way, after Windows started, the startup_db.cmd file is run and the instance is brought up.

    Again, this is a workaround, the problem still exists. I think that a different init.ora is used when starting the instance automatically after rebooting the machine, but you know your situation best.

    Good luck,

    Edwin

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •