This discussion is archived
8 Replies Latest reply: Jan 27, 2013 11:49 AM by yoonas RSS

Can't access 'Get started' anymore...

987395 Newbie
Currently Being Moderated
Hello forum!

I have installed Oracle 11g r2, worked on it, created a schema and almost finished a project. (By the way, I'm a student and I need this for school. This was a school project about a Hotel Chain)
But now I can't access anymore http://127.0.0.1:8080/apex/f?p=4950 (this thing happened suddenly, I finished working Friday and today I wanted to log in and I couldn't)
Firefox says:
Unable to connect

Firefox can't establish a connection to the server at 127.0.0.1:8080.
The site could be temporarily unavailable or too busy. Try again in a few
moments.
If you are unable to load any pages, check your computer's network
connection.
If your computer or network is protected by a firewall or proxy, make sure
that Firefox is permitted to access the Web.

Tried all the browsers I have installed on my laptop. None of them worked. I am a newbye and I don't know much about these things...
I have googled the problem but all the people with the same issue couldn't start get started from the beggining (after install)

Please help me, I have worked so much at this project...
  • 1. Re: Can't access 'Get started' anymore...
    yoonas Expert
    Currently Being Moderated
    Hi,

    Please provide complete details, database version, apex version, os etc

    https://blogs.oracle.com/shay/entry/10_commandments_for_the_otn_fo


    As you have posted under XE i guess you have installed 11g express edition.

    Did you make any changes ?

    If it is on windows check if oracle database is running

    Run>services.msc - You can search for "OracleServiceXE" and "OracleXETNSListener" services, see if they are running (If it is not running try to start with "start database" from your installation shortcuts)

    Post the output of these commands
    Run > sqlplus <username>/<password>
    Run>cmd>lsnrctl status

    Regards
    Yoonas

    Edited by: yoonus on Jan 27, 2013 10:10 AM
  • 2. Re: Can't access 'Get started' anymore...
    987395 Newbie
    Currently Being Moderated
    I'm running Oracle 11g R2, XE in Windows 8, 32 bits.
    Both of the services are running
    Microsoft Windows [Version 6.2.9200]
    (c) 2012 Microsoft Corporation. All rights reserved.

    C:\Users\Ionut>lsnrctl status

    LSNRCTL for 32-bit Windows: Version 11.2.0.2.0 - Production on 27-IAN-2013 20:08
    :29

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

    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1)))
    STATUS of the LISTENER
    ------------------------
    Alias LISTENER
    Version TNSLSNR for 32-bit Windows: Version 11.2.0.2.0 - Produ
    ction
    Start Date 16-IAN-2013 18:09:09
    Uptime 11 days 1 hr. 59 min. 23 sec
    Trace Level off
    Security ON: Local OS Authentication
    SNMP OFF
    Default Service XE
    Listener Parameter File C:\oraclexe\app\oracle\product\11.2.0\server\network\a
    dmin\listener.ora
    Listener Log File C:\oraclexe\app\oracle\diag\tnslsnr\IonutPC\listener\a
    lert\log.xml
    Listening Endpoints Summary...
    (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC1ipc)))
    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=IonutPC)(PORT=1521)))
    Services Summary...
    Service "CLRExtProc" has 1 instance(s).
    Instance "CLRExtProc", status UNKNOWN, has 1 handler(s) for this service...
    Service "PLSExtProc" has 1 instance(s).
    Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
    The command completed successfully

    C:\Users\Ionut>

    This was for Run>cmd>lsnrctl status
    This is for Run > sqlplus <username>/<password>

    SQL*Plus: Release 11.2.0.2.0 Production on D Ian 27 20:14:46 2013

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

    Enter user-name: IONUT
    Enter password:
    ERROR:
    ORA-01034: ORACLE not available
    ORA-27101: shared memory realm does not exist
    Process ID: 0
    Session ID: 0 Serial number: 0


    Enter user-name:

    I'm not sure I did the right thing at the second command. This is the user-name I used to log in the schema. I have also tried with sys and I could catch a glipmse with something like CONNECTED before the console to dissapear...
  • 3. Re: Can't access 'Get started' anymore...
    yoonas Expert
    Currently Being Moderated
    Service is running but database is not up yet

    start>cmd> sqlplus / as sysdba
    enter "startup" in sqlplus to start the database
    startup
    Post the output

    Edited by: yoonus on Jan 27, 2013 10:36 AM
  • 4. Re: Can't access 'Get started' anymore...
    987395 Newbie
    Currently Being Moderated
    Microsoft Windows [Version 6.2.9200]
    (c) 2012 Microsoft Corporation. All rights reserved.

    C:\Users\Ionut>sqlplus / as sysdba

    SQL*Plus: Release 11.2.0.2.0 Production on D Ian 27 20:38:03 2013

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

    Connected to an idle instance.

    SQL> startup
    ORA-03113: end-of-file on communication channel
    SQL>
  • 5. Re: Can't access 'Get started' anymore...
    yoonas Expert
    Currently Being Moderated
    Restart the Pc
    check for the services
    try connecting to sqlplus with your username/password
    if not connecting do sqlplus / as sysdba and startup

    post the output from the above command and also post contents of alert log file(last portion) <C:\oraclexe\app\oracle\diag\rdbms\xe\xe\trace>\alert_xe.log

    If your location is different make necessary changes in the alert log file path.
  • 6. Re: Can't access 'Get started' anymore...
    987395 Newbie
    Currently Being Moderated
    Both sevices are running.

    Microsoft Windows [Version 6.2.9200]
    (c) 2012 Microsoft Corporation. All rights reserved.

    C:\Users\Ionut>sqlplus / as sysdba

    SQL*Plus: Release 11.2.0.2.0 Production on D Ian 27 21:28:03 2013

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


    Connected to:
    Oracle Database 11g Express Edition Release 11.2.0.2.0 - Production

    SQL> startup
    ORA-01081: cannot start already-running ORACLE - shut it down first
    SQL>

    Maybe it is to much

    Sat Jan 26 19:17:43 2013
    Errors in file C:\ORACLEXE\APP\ORACLE\diag\rdbms\xe\xe\trace\xe_m002_584.trc (incident=6674):
    ORA-00600: internal error code, arguments: [kghfrh:ds], [0x28E2A940], [], [], [], [], [], [], [], [], [], []
    ORA-00600: internal error code, arguments: [kghfrh:ds], [0x28E2A940], [], [], [], [], [], [], [], [], [], []
    Incident details in: C:\ORACLEXE\APP\ORACLE\diag\rdbms\xe\xe\incident\incdir_6674\xe_m002_584_i6674.trc
    Use ADRCI or Support Workbench to package the incident.
    See Note 411.1 at My Oracle Support for error and packaging details.
    Errors in file C:\ORACLEXE\APP\ORACLE\diag\rdbms\xe\xe\trace\xe_m002_584.trc (incident=6675):
    ORA-00603: ORACLE server session terminated by fatal error
    ORA-24557: error 600 encountered while handling error 600; exiting server process
    ORA-00600: internal error code, arguments: [kghfrh:ds], [0x28E2A940], [], [], [], [], [], [], [], [], [], []
    ORA-00600: internal error code, arguments: [kghfrh:ds], [0x28E2A940], [], [], [], [], [], [], [], [], [], []
    Incident details in: C:\ORACLEXE\APP\ORACLE\diag\rdbms\xe\xe\incident\incdir_6675\xe_m002_584_i6675.trc
    Dumping diagnostic data in directory=[cdmp_20130126191745], requested by (instance=1, osid=584 (M002)), summary=[incident=6674].
    opidrv aborting process M002 ospid (584) as a result of ORA-603
    Dumping diagnostic data in directory=[cdmp_20130126191747], requested by (instance=1, osid=584 (M002)), summary=[incident=6675].
    Sat Jan 26 19:17:49 2013
    Errors in file C:\ORACLEXE\APP\ORACLE\diag\rdbms\xe\xe\trace\xe_pmon_2416.trc (incident=6417):
    ORA-00600: internal error code, arguments: [kghfrh:ds], [0x28E2A940], [], [], [], [], [], [], [], [], [], []
    Incident details in: C:\ORACLEXE\APP\ORACLE\diag\rdbms\xe\xe\incident\incdir_6417\xe_pmon_2416_i6417.trc
    Use ADRCI or Support Workbench to package the incident.
    See Note 411.1 at My Oracle Support for error and packaging details.
    Errors in file C:\ORACLEXE\APP\ORACLE\diag\rdbms\xe\xe\trace\xe_pmon_2416.trc:
    ORA-00600: internal error code, arguments: [kghfrh:ds], [0x28E2A940], [], [], [], [], [], [], [], [], [], []
    PMON (ospid: 2416): terminating the instance due to error 472
    System state dump requested by (instance=1, osid=2416 (PMON)), summary=[abnormal instance termination].
    System State dumped to trace file C:\ORACLEXE\APP\ORACLE\diag\rdbms\xe\xe\trace\xe_diag_2436.trc
    Dumping diagnostic data in directory=[cdmp_20130126191751], requested by (instance=1, osid=2416 (PMON)), summary=[abnormal instance termination].
    Sat Jan 26 19:18:06 2013
    Instance terminated by PMON, pid = 2416
    Sun Jan 27 19:14:28 2013
    Starting ORACLE instance (normal)
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    Picked latch-free SCN scheme 2
    Using LOG_ARCHIVE_DEST_1 parameter default value as USE_DB_RECOVERY_FILE_DEST
    Autotune of undo retention is turned on.
    IMODE=BR
    ILAT =18
    LICENSE_MAX_USERS = 0
    SYS auditing is disabled
    Starting up:
    Oracle Database 11g Express Edition Release 11.2.0.2.0 - Production.
    Using parameter settings in server-side pfile C:\ORACLEXE\APP\ORACLE\PRODUCT\11.2.0\SERVER\DATABASE\INITXE.ORA
    System parameters with non-default values:
    sessions = 172
    spfile = "C:\ORACLEXE\APP\ORACLE\PRODUCT\11.2.0\SERVER\DBS\SPFILEXE.ORA"
    memory_target = 1G
    control_files = "C:\ORACLEXE\APP\ORACLE\ORADATA\XE\CONTROL.DBF"
    compatible = "11.2.0.0.0"
    db_recovery_file_dest = "C:\oraclexe\app\oracle\fast_recovery_area"
    db_recovery_file_dest_size= 10G
    undo_management = "AUTO"
    undo_tablespace = "UNDOTBS1"
    remote_login_passwordfile= "EXCLUSIVE"
    dispatchers = "(PROTOCOL=TCP) (SERVICE=XEXDB)"
    shared_servers = 4
    job_queue_processes = 4
    audit_file_dest = "C:\ORACLEXE\APP\ORACLE\ADMIN\XE\ADUMP"
    db_name = "XE"
    open_cursors = 300
    diagnostic_dest = "C:\ORACLEXE\APP\ORACLE"
    Sun Jan 27 19:14:50 2013
    PMON started with pid=2, OS id=7316
    Sun Jan 27 19:14:50 2013
    PSP0 started with pid=3, OS id=1876
    Sun Jan 27 19:14:52 2013
    VKTM started with pid=4, OS id=8156 at elevated priority
    VKTM running at (10)millisec precision with DBRM quantum (100)ms
    Sun Jan 27 19:14:52 2013
    DBRM started with pid=7, OS id=2440
    Sun Jan 27 19:14:52 2013
    GEN0 started with pid=5, OS id=2468
    Sun Jan 27 19:14:52 2013
    DIA0 started with pid=8, OS id=1316
    Sun Jan 27 19:14:52 2013
    DIAG started with pid=6, OS id=3936
    Sun Jan 27 19:14:52 2013
    MMAN started with pid=9, OS id=2332
    Sun Jan 27 19:14:54 2013
    USER (ospid: 7172): terminating the instance due to error 443
    Instance terminated by USER, pid = 7172
    Sun Jan 27 21:20:20 2013
    Starting ORACLE instance (normal)
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    Picked latch-free SCN scheme 2
    Using LOG_ARCHIVE_DEST_1 parameter default value as USE_DB_RECOVERY_FILE_DEST
    Autotune of undo retention is turned on.
    IMODE=BR
    ILAT =18
    LICENSE_MAX_USERS = 0
    SYS auditing is disabled
    Starting up:
    Oracle Database 11g Express Edition Release 11.2.0.2.0 - Production.
    Using parameter settings in server-side pfile C:\ORACLEXE\APP\ORACLE\PRODUCT\11.2.0\SERVER\DATABASE\INITXE.ORA
    System parameters with non-default values:
    sessions = 172
    spfile = "C:\ORACLEXE\APP\ORACLE\PRODUCT\11.2.0\SERVER\DBS\SPFILEXE.ORA"
    memory_target = 1G
    control_files = "C:\ORACLEXE\APP\ORACLE\ORADATA\XE\CONTROL.DBF"
    compatible = "11.2.0.0.0"
    db_recovery_file_dest = "C:\oraclexe\app\oracle\fast_recovery_area"
    db_recovery_file_dest_size= 10G
    undo_management = "AUTO"
    undo_tablespace = "UNDOTBS1"
    remote_login_passwordfile= "EXCLUSIVE"
    dispatchers = "(PROTOCOL=TCP) (SERVICE=XEXDB)"
    shared_servers = 4
    job_queue_processes = 4
    audit_file_dest = "C:\ORACLEXE\APP\ORACLE\ADMIN\XE\ADUMP"
    db_name = "XE"
    open_cursors = 300
    diagnostic_dest = "C:\ORACLEXE\APP\ORACLE"
    Sun Jan 27 21:20:38 2013
    PMON started with pid=2, OS id=3928
    Sun Jan 27 21:20:38 2013
    PSP0 started with pid=3, OS id=3932
    Sun Jan 27 21:20:40 2013
    VKTM started with pid=4, OS id=3968 at elevated priority
    VKTM running at (10)millisec precision with DBRM quantum (100)ms
    Sun Jan 27 21:20:40 2013
    MMAN started with pid=9, OS id=3988
    Sun Jan 27 21:20:41 2013
    DBW0 started with pid=10, OS id=3992
    Sun Jan 27 21:20:41 2013
    RECO started with pid=14, OS id=4008
    Sun Jan 27 21:20:40 2013
    GEN0 started with pid=5, OS id=3972
    Sun Jan 27 21:20:41 2013
    LGWR started with pid=11, OS id=3996
    Sun Jan 27 21:20:41 2013
    MMON started with pid=15, OS id=4012
    Sun Jan 27 21:20:40 2013
    DIAG started with pid=6, OS id=3976
    Sun Jan 27 21:20:41 2013
    SMON started with pid=13, OS id=4004
    Sun Jan 27 21:20:40 2013
    DBRM started with pid=7, OS id=3980
    Sun Jan 27 21:20:41 2013
    CKPT started with pid=12, OS id=4000
    Sun Jan 27 21:20:40 2013
    DIA0 started with pid=8, OS id=3984
    Sun Jan 27 21:20:41 2013
    MMNL started with pid=16, OS id=4016
    Sun Jan 27 21:20:46 2013
    Sweep [inc][6675]: completed
    Sun Jan 27 21:20:41 2013
    starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
    starting up 4 shared server(s) ...
    ORACLE_BASE from environment = C:\oraclexe\app\oracle
    Sun Jan 27 21:20:46 2013
    alter database mount exclusive
    Sweep [inc][6674]: completed
    Sweep [inc][6673]: completed
    Sweep [inc][6417]: completed
    Sweep [inc2][6675]: completed
    Sweep [inc2][6674]: completed
    Sweep [inc2][6673]: completed
    Sweep [inc2][6417]: completed
    Successful mount of redo thread 1, with mount id 2686972142
    Database mounted in Exclusive Mode
    Lost write protection disabled
    Completed: alter database mount exclusive
    alter database open
    Beginning crash recovery of 1 threads
    Started redo scan
    Completed redo scan
    read 414 KB redo, 127 data blocks need recovery
    Started redo application at
    Thread 1: logseq 17, block 16568
    Recovery of Online Redo Log: Thread 1 Group 1 Seq 17 Reading mem 0
    Mem# 0: C:\ORACLEXE\APP\ORACLE\FAST_RECOVERY_AREA\XE\ONLINELOG\O1_MF_1_8FV49MMY_.LOG
    Completed redo application of 0.32MB
    Completed crash recovery at
    Thread 1: logseq 17, block 17396, scn 765518
    127 data blocks read, 127 data blocks written, 414 redo k-bytes read
    Sun Jan 27 21:20:53 2013
    Thread 1 advanced to log sequence 18 (thread open)
    Thread 1 opened at log sequence 18
    Current log# 2 seq# 18 mem# 0: C:\ORACLEXE\APP\ORACLE\FAST_RECOVERY_AREA\XE\ONLINELOG\O1_MF_2_8FV49OKJ_.LOG
    Successful open of redo thread 1
    Sun Jan 27 21:20:54 2013
    SMON: enabling cache recovery
    [4080] Successfully onlined Undo Tablespace 2.
    Undo initialization finished serial:0 start:110921 end:111015 diff:94 (0 seconds)
    Verifying file header compatibility for 11g tablespace encryption..
    Verifying 11g file header compatibility for tablespace encryption completed
    SMON: enabling tx recovery
    Database Characterset is AL32UTF8
    Opening with Resource Manager plan: INTERNAL_PLAN_XE
    Sun Jan 27 21:20:55 2013
    Starting background process VKRM
    Sun Jan 27 21:20:55 2013
    VKRM started with pid=17, OS id=1312
    replication_dependency_tracking turned off (no async multimaster replication found)
    Starting background process QMNC
    Sun Jan 27 21:20:55 2013
    QMNC started with pid=24, OS id=1200
    Completed: alter database open
    Sun Jan 27 21:21:02 2013
    Starting background process CJQ0
    Sun Jan 27 21:21:02 2013
    CJQ0 started with pid=28, OS id=3332
    Sun Jan 27 21:21:03 2013
    db_recovery_file_dest_size of 10240 MB is 0.98% used. This is a
    user-specified limit on the amount of space that will be used by this
    database for recovery-related files, and does not reflect the amount of
    space available in the underlying filesystem or ASM diskgroup.
    Setting Resource Manager plan SCHEDULER[0x30FD]:DEFAULT_MAINTENANCE_PLAN via scheduler window
    Sun Jan 27 21:21:23 2013
    Errors in file C:\ORACLEXE\APP\ORACLE\diag\rdbms\xe\xe\trace\xe_j000_5236.trc:
    ORA-12012: error on auto execute of job "SYS"."BSLN_MAINTAIN_STATS_JOB"
    ORA-06550: line 1, column 807:
    PLS-00201: identifier 'DBSNMP.BSLN_INTERNAL' must be declared
    ORA-06550: line 1, column 807:
    PL/SQL: Statement ignored
    Sun Jan 27 21:21:32 2013
    Starting background process SMCO
    Sun Jan 27 21:21:32 2013
    SMCO started with pid=26, OS id=5724
    Sun Jan 27 21:28:15 2013
    Starting ORACLE instance (normal)
  • 7. Re: Can't access 'Get started' anymore...
    987395 Newbie
    Currently Being Moderated
    I don't know what happened but it's working now.
    Thanks a lot!
  • 8. Re: Can't access 'Get started' anymore...
    yoonas Expert
    Currently Being Moderated
    Run > sqlplus <username>/<password> - Did you try to connect this way ? , just try this way and run any sql statement (select sysdate from dual)

    Try your apex page now

    Run>cmd>lsnrctl status - post the output



    If its already working mark the thread as answered

    Edited by: yoonus on Jan 27, 2013 11:39 AM

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points