Error at line 1 ora 01034 oracle not available

Hello, I have Oracle 11g release 2 installed on linux redhat 5, big learning curve since i am use to windows, but linux i hear is much bettter. so anyways i have installed oracle 11g release but, but...

Hello,

I have Oracle 11g release 2 installed on linux redhat 5, big learning curve since i am use to windows, but linux i hear is much bettter. so anyways i have installed oracle 11g release but, but ran into some errors when installing which are bleow:

Hard limit: maximum open file descriptors
OS Kernal Parameter: ip_local_port_range
OS Kernal Parameter: aio-max-nr

also:
Package: libaio-devel-0.3.106
Package: sysstat-7.0.2
Package:unitODBC-2.2.11
Package:unixODBC-devel-2.2.11

I fixed the top three when i googled each error, then i did the fix, but when i go to re-run the install the top 3 errors still came, not sure why, so i hit ignore them and continue install. So now when i log into sysdba, using command on oracle account i type in terminal:
sqlplus / as sysdba

then i type select * from v$version;
but when i do it says:
*
ERROR at line 1:
ORA-01034: ORACLE not available
Process ID: 0
Session ID: 0 Serial number: 0

Does anyone know why i am getting this, is it because of the error message from the install? and if you need logs where can i locate them at on this linux pc? was it a good idea to go and install oracle on a linux box, or would windows be just as good?

thanks in advance all

sorry i am a noob (but a network engineer) wanting to become a dba :)

ORA-01034 means that the command you want to perform cannot be done in a stop, idle or shutdown database. If you’re surprised by the error, maybe you should check the database status immediately. It maybe someone or something turn it off without notification.

Connect to Local Database

Let’s see a case. Tried to connect to the local database.

[oracle@test ~]$ sqlplus system
...
Enter password:
ERROR:
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
Linux-x86_64 Error: 2: No such file or directory
Additional information: 4376
Additional information: -1649756641
Process ID: 0
Session ID: 0 Serial number: 0

Because the database is stop there’s no way to do authentication.

Let’s see another case.

[oracle@test ~]$ sqlplus / as sysdba
...
SQL> alter database begin backup;
alter database begin backup
*
ERROR at line 1:
ORA-01034: ORACLE not available
Process ID: 0
Session ID: 0 Serial number: 0

Although we can connect to the database by OS authentication, we cannot perform any database operation.

The solution is to startup the database.

Data Guard

If you saw ORA-01034 in the alert log, don’t panic, it’s not generated from the database that you are currently running. It’s usually from the standby Database.

...
Tue Oct 13 14:35:08 2008
Errors in file /oracle/admin/ORCL1/bdump/orcl1_arc1_3295892.trc:
ORA-01034: ORACLE not available

In such case, the primary database tried to transport redo log to the standby database, but the standby database is stop for some reason. You need to check what’s going on.

I installed oracle 12c r2 in ubuntu 18.04 and when I enter SqlPlus and execute a query it gives me error.

To install the oracle I followed these two guides:

1- https://tutorialforlinux.com/2018/05/09/how-to-install-oracle-12c-r2-database-on-ubuntu-18-04-bionic-64bit-easy-guide/
2- https://etc.to/confluence/pages/viewpage.action?pageId=20480023

The error that gives me is the following:

ERROR at line 1:
ORA-01034:ORACLE not available
Process ID:0
Session ID: Serial numbre:0

The status of the listener (lsnrctl status) gives me the following error:

Connectinc to (ADDRESS=(PROTOCOL=tcp)(HOST)(PORT=1521))
TNS-12541:TNS: no listener
tns-12560 TNS:protocol adapter error
TNS-00511: No listener
Linux error:111: Connection refused

Can anybody help me?Thanks!!

MORE INFO

now when I put lsnrctl status I get this, but in sqlplus the failure of above still appears

LSNRCTL for Linux: Version 12.2.0.1.0 - Production on 19-OCT-2018 01:53:18

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

Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
STATUS of the LISTENER
------------------------
Alias                     LISTENER
Version                   TNSLSNR for Linux: Version 12.2.0.1.0 - Production
Start Date                19-OCT-2018 01:52:14
Uptime                    0 days 0 hr. 1 min. 5 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Log File         /u01/app/oracle/diag/tnslsnr/andoni-VirtualBox/listener/alert/log.xml
Listening Endpoints Summary...
  (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=andoni-VirtualBox)(PORT=1521)))
The listener supports no services
The command completed successfully

Startup error:

    Enter user-name: sys as sysdba
Enter password:
Connected to an idle instance.

SQL> startup
ORA-01078: failure in processing system parameters
LRM-00109: could not open parameter file '/u01/app/oracle/product/12/dbhome_1/dbs/initSID.ora'
SQL>

Здравствуйте, уважаемые коллеги. Хочу поделиться сегодня с вами ситуацией, с которой столкнулся при подключении к базе данных Oracle 12c из стороннего клиентского приложения (архитектура клиент-сервер). При отладке приложения и запуске команды running fnd_nodes cleanup получил ошибку:

ERROR:
ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist SVR4 Error: 2: No such file or directory

При этом я вполне мог подключиться к базе данных и выполнить autoconfig на стороне базы. Но на стороне приложения все также вылетали ошибки  и я не смог подключиться к БД из приложения. При этом база данных Oracle запущена и работает штатно.

Честно говоря, я не особо понял причину этой ошибки. Я проверил файлы XML и DBC, файл TNSNAME и listener, но я понять ничего не смог. Все в норме.

Причина ошибки ORA-01034 и ORA-2710

Поколупавшись еще немного в интернете и своих мозгах, я понял эти ошибки связаны с ограниченной сессией к базе данных (db restricted session). Для того, чтобы запустить adstats.sql в приложении, я должен был разрешить ограниченную сессию к ДБ (restricted session). Но я забыл закрыть ее после того, как запустил adstats.sql. Это и вызывало ошибки.

Как исправить ошибки ORA-01034 и ORA-2710

Просто я отключился от БД один раз (закрыл сессию), так как я не мог выяснить причину проблемы сразу в процессе устранения неполадок. После этого эта ошибка исчезла.

Также вы можете выполнить следующую команду, чтобы избежать этой ошибки и без  необходимости в закрытии сессии:

SQL> alter disable restricted session;

Вас заинтересует / Intresting for you:

database_1  | ORACLE PASSWORD FOR SYS AND SYSTEM: test
database_1  | 
database_1  | Oracle Database 11g Express Edition Configuration
database_1  | -------------------------------------------------
database_1  | This will configure on-boot properties of Oracle Database 11g Express 
database_1  | Edition.  The following questions will determine whether the database should 
database_1  | be starting upon system boot, the ports it will use, and the passwords that 
database_1  | will be used for database accounts.  Press <Enter> to accept the defaults. 
database_1  | Ctrl-C will abort.
database_1  | 
database_1  | Specify the HTTP port that will be used for Oracle Application Express [8080]:
database_1  | Specify a port that will be used for the database listener [1521]:
database_1  | Specify a password to be used for database accounts.  Note that the same
database_1  | password will be used for SYS and SYSTEM.  Oracle recommends the use of 
database_1  | different passwords for each database account.  This can be done after 
database_1  | initial configuration:
database_1  | Confirm the password:
database_1  | 
database_1  | Do you want Oracle Database 11g Express Edition to be started on boot (y/n) [y]:
database_1  | Starting Oracle Net Listener...Done
database_1  | Configuring database...Done
database_1  | Starting Oracle Database 11g Express Edition instance...Done
database_1  | Installation completed successfully.
database_1  | 
database_1  | SQL*Plus: Release 11.2.0.2.0 Production on Wed Nov 29 11:59:08 2017
database_1  | 
database_1  | Copyright (c) 1982, 2011, Oracle.  All rights reserved.
database_1  | 
database_1  | Connected to an idle instance.
database_1  | 
database_1  | SQL> BEGIN DBMS_XDB.SETLISTENERLOCALACCESS(FALSE); END;
database_1  | 
database_1  | *
database_1  | ERROR at line 1:
database_1  | ORA-01034: ORACLE not available
database_1  | Process ID: 0
database_1  | Session ID: 0 Serial number: 0
database_1  | 
database_1  | 
database_1  | SQL> SQL>       ALTER DATABASE ADD LOGFILE GROUP 4 ('/u01/app/oracle/oradata/xe/redo04.log') SIZE 50m
database_1  | *
database_1  | ERROR at line 1:
database_1  | ORA-01034: ORACLE not available
database_1  | Process ID: 0
database_1  | Session ID: 0 Serial number: 0
database_1  | 
database_1  | 
database_1  | SQL>       ALTER DATABASE ADD LOGFILE GROUP 5 ('/u01/app/oracle/oradata/xe/redo05.log') SIZE 50m
database_1  | *
database_1  | ERROR at line 1:
database_1  | ORA-01034: ORACLE not available
database_1  | Process ID: 0
database_1  | Session ID: 0 Serial number: 0
database_1  | 
database_1  | 
database_1  | SQL> Disconnected
database_1  | mv: cannot stat '/u01/app/oracle/product/11.2.0/xe/dbs/spfilexe.ora': No such file or directory
database_1  | mv: cannot stat '/u01/app/oracle/product/11.2.0/xe/dbs/orapwxe': No such file or directory
database_1  | #########################
database_1  | DATABASE IS READY TO USE!
database_1  | #########################
database_1  | DONE: Executing user defined scripts
database_1  | 
database_1  | The following output is now a tail of the alert.log:
database_1  | QMNC started with pid=24, OS id=770 
database_1  | Completed: ALTER DATABASE OPEN
database_1  | Wed Nov 29 11:59:06 2017
database_1  | db_recovery_file_dest_size of 10240 MB is 0.98% used. This is a
database_1  | user-specified limit on the amount of space that will be used by this
database_1  | database for recovery-related files, and does not reflect the amount of
database_1  | space available in the underlying filesystem or ASM diskgroup.
database_1  | Starting background process CJQ0
database_1  | Wed Nov 29 11:59:06 2017
database_1  | CJQ0 started with pid=25, OS id=784 
database_1  | Wed Nov 29 12:09:06 2017
database_1  | Starting background process SMCO
database_1  | Wed Nov 29 12:09:06 2017
database_1  | SMCO started with pid=28, OS id=1080 

I’m trying to install Oracle Database 11g Express Edition on my ubuntu server. After running command:

sudo service oracle-xe start

I get following result after configuration:

Starting Oracle Net Listener...Done
Configuring database...
Database Configuration failed.  Look into /u01/app/oracle/product/11.2.0/xe/config/log for de                                                                              tails

in log files I found the following informations:

CloneRmanRestore.log:

    LRM-00116: syntax error at 'sessions' following '='
ORA-01078: failure in processing system parameters
select TO_CHAR(systimestamp,'YYYYMMDD HH:MI:SS') from dual
*
ERROR at line 1:
ORA-01034: ORACLE not available
Process ID: 0
Session ID: 0 Serial number: 0


declare
*
ERROR at line 1:
ORA-01034: ORACLE not available
Process ID: 0
Session ID: 0 Serial number: 0


select TO_CHAR(systimestamp,'YYYYMMDD HH:MI:SS') from dual
*
ERROR at line 1:
ORA-01034: ORACLE not available
Process ID: 0
Session ID: 0 Serial number: 0

postDBCreation.log

begin
*
ERROR at line 1:
ORA-01034: ORACLE not available
Process ID: 0
Session ID: 0 Serial number: 0


create spfile='/u01/app/oracle/product/11.2.0/xe/dbs/spfileXE.ora' FROM pfile='/u01/app/oracle/product/11.2.0/xe/config/scripts/init.ora'
*
ERROR at line 1:
ORA-01078: failure in processing system parameters
LRM-00116: syntax error at 'sessions' following '='


ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
Linux-x86_64 Error: 2: No such file or directory
ORA-01078: failure in processing system parameters
LRM-00109: could not open parameter file '/u01/app/oracle/product/11.2.0/xe/dbs/initXE.ora'
select 'utl_recomp_begin: ' || to_char(sysdate, 'HH:MI:SS') from dual
*
ERROR at line 1:
ORA-01034: ORACLE not available
Process ID: 0
Session ID: 0 Serial number: 0


BEGIN utl_recomp.recomp_serial(); END;

*
ERROR at line 1:
ORA-01034: ORACLE not available
Process ID: 0
Session ID: 0 Serial number: 0


select 'utl_recomp_end: ' || to_char(sysdate, 'HH:MI:SS') from dual
*
ERROR at line 1:
ORA-01034: ORACLE not available
Process ID: 0
Session ID: 0 Serial number: 0

cloneDBCreation.log:

Create controlfile reuse set database "XE"
*
ERROR at line 1:
ORA-01034: ORACLE not available
Process ID: 0
Session ID: 0 Serial number: 0


BEGIN dbms_backup_restore.zerodbid(0); END;

*
ERROR at line 1:
ORA-01034: ORACLE not available
Process ID: 0
Session ID: 0 Serial number: 0


ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
Linux-x86_64 Error: 2: No such file or directory
LRM-00116: syntax error at 'sessions' following '='
ORA-01078: failure in processing system parameters
Create controlfile reuse set database "XE"
*
ERROR at line 1:
ORA-01034: ORACLE not available
Process ID: 0
Session ID: 0 Serial number: 0


alter system enable restricted session
*
ERROR at line 1:
ORA-01034: ORACLE not available
Process ID: 0
Session ID: 0 Serial number: 0


alter database "XE" open resetlogs
*
ERROR at line 1:
ORA-01034: ORACLE not available
Process ID: 0
Session ID: 0 Serial number: 0

postDBCreation.log:
begin
*
ERROR at line 1:
ORA-01034: ORACLE not available
Process ID: 0
Session ID: 0 Serial number: 0


create spfile='/u01/app/oracle/product/11.2.0/xe/dbs/spfileXE.ora' FROM pfile='/u01/app/oracle/product/11.2.0/xe/config/scripts/init.ora'
*
ERROR at line 1:
ORA-01078: failure in processing system parameters
LRM-00116: syntax error at 'sessions' following '='


ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
Linux-x86_64 Error: 2: No such file or directory
ORA-01078: failure in processing system parameters
LRM-00109: could not open parameter file '/u01/app/oracle/product/11.2.0/xe/dbs/initXE.ora'
select 'utl_recomp_begin: ' || to_char(sysdate, 'HH:MI:SS') from dual
*
ERROR at line 1:
ORA-01034: ORACLE not available
Process ID: 0
Session ID: 0 Serial number: 0


BEGIN utl_recomp.recomp_serial(); END;

*
ERROR at line 1:
ORA-01034: ORACLE not available
Process ID: 0
Session ID: 0 Serial number: 0


select 'utl_recomp_end: ' || to_char(sysdate, 'HH:MI:SS') from dual
*
ERROR at line 1:
ORA-01034: ORACLE not available
Process ID: 0
Session ID: 0 Serial number: 0

postScripts.log:

CREATE OR REPLACE LIBRARY dbms_sumadv_lib AS '/u01/app/oracle/product/11.2.0/xe/lib/libqsmashr.so';
*
ERROR at line 1:
ORA-01034: ORACLE not available
Process ID: 0
Session ID: 0 Serial number: 0


BEGIN dbms_datapump_utl.replace_default_dir; END;

*
ERROR at line 1:
ORA-01034: ORACLE not available
Process ID: 0
Session ID: 0 Serial number: 0


commit
*
ERROR at line 1:
ORA-01034: ORACLE not available
Process ID: 0
Session ID: 0 Serial number: 0


create or replace directory XMLDIR as '/u01/app/oracle/product/11.2.0/xe/rdbms/xml'
*
ERROR at line 1:
ORA-01034: ORACLE not available
Process ID: 0
Session ID: 0 Serial number: 0


DROP DIRECTORY ORACLE_OCM_CONFIG_DIR
*
ERROR at line 1:
ORA-01034: ORACLE not available
Process ID: 0
Session ID: 0 Serial number: 0


DROP DIRECTORY ADMIN_DIR
*
ERROR at line 1:
ORA-01034: ORACLE not available

How can I fix it and configure my database? I have 256 MB of RAM memory, is it enough to run Oracle? Can it be an issue?

oracle tutorial webinars

As mentioned in the previous ORA-03113: End of File on Communication Channel article, a vast majority of errors in Oracle can be divided into two categories. The first of which are errors caused by syntax issues, often small user-generated mistakes in typing or issuing commands. The second types are errors in the network, typically revolving around connectivity issues or memory space management. The ORA-01034 falls into this latter category as a primarily storage-based error.

Causes

An ORA-01034 error is triggered due to the Oracle system not being available or started up. This could derive from the System Global Area (SGA) necessitating more storage space than what is currently being allocated for your Oracle database. It could also be that operating system variable pointing to the instance was not properly defined. The error could also result during an upgrade of your Oracle systems.

Solutions

The ORA-01034 is almost always accompanied with additional error messages, often times ORA-27101: shared memory realm. You can utilize these additional errors to pinpoint the source of the ORA-01034. For example, the aforementioned ORA-27101 would indicate that the ORA-01034 error could derive from the database parameters of your SGA being modified and no longer holding a proper amount of storage. You can go back and reissue the original parameters to potentially resolve this issue.

You should also check to make sure ORACLE_HOME and ORACLE_SID properly match. ORACLE_SID is the instance pointer mentioned before. Be sure that ORACLE_HOME is not followed by a trailing slash at the end. Search for ORACLE_SID using ‘echo $ORACLE_SID’ for Unix and by right-clicking the My Computer tab in Windows, clicking on Properties, then the Advance tab, and finally the Environment variable. You may find that ORACLE_SID is undefined or left blank, which is causing your ORA-01034 error.

If you believe the problem is the result of upgrading Oracle, you can check two files (/etc/oratab and /var/opt/oracle/oratab) for an invalid entry. Match the ORACLE_HOME and ORACLE_SID in these files. If they do not match, this needs to be resolved in order to resolve the error.

Looking forward

This type of error is fairly easy to pinpoint due to the accompanying errors matter, but even still it can be a good idea to prevent the error from happening in the first place. Remaining aware of all modifications made to the SGA parameters and keeping a steady eye on the storage space in your Oracle systems can mitigate the insufficient memory aspect of the ORA-01034. If you are using Windows, taking steps like cleaning out your Windows Event Log from time to time can go a long way in saving you time and headaches. If you find that you are continuing to have difficulties with properly partitioning your storage, a licensed Oracle consulting firm can aid in training your team on the finer points of Oracle database management.

Если не хочется пользоваться темой «Полезные ссылки», то вот выдержки программы Oracle Error Messages Viewer

Цитата:

Message
ORA-01034:ORACLE not available
Cause
Oracle was not started. Possible causes include the following: The SGA requires more space than was allocated for it. The operating-system variable pointing to the instance is improperly defined.
Action
Refer to accompanying messages for possible causes and correct the problem mentioned in the other messages. If Oracle has been initialized, then on some operating systems, verify that Oracle was linked correctly. See the platform-specific Oracle documentation.

Из собственного опыта и данной цытаты могу сделать вывод, что Сервис базы запускается, но НЕ сама база (она может находиться в статусе nomount, mount, но никак не open).

Возможные причины: да куча целая, как указал baggio неправильно сконфигурированы сеть в оракловых файлах.
также если база проинициализировалась, но сервера не цепляются (т.е. между инициализацией и запуском супермажных серверов ничего другого не далали), можно допускать падение базы. Т.е. эта ошибка следствие, необходимо искать причину

Рекомендации:
использовать утилиту tnsping для поверки доступности базы по указанным в сетевых конфигах адресам.
Смотреть alert.log на наличие ошибок, смотреть sqlnet.log в каталоге запуска приложений, т.к. мы говорим про супермажные сервисы, скорее всего будет в sm2000/bin.

ORA-01034: ORACLE not available
Cause: Oracle was not started up. Possible causes include the following:
— The SGA requires more space than was allocated for it.
— The operating-system variable pointing to the instance is improperly defined.
Action: Refer to accompanying messages for possible causes and correct the problem mentioned in the other messages. If Oracle has been initialized, then on some operating systems, verify that Oracle was linked correctly. See the platform specific Oracle documentation.

Reference: Oracle Documentation

There could be a many reasons for ORA-01034, some of them are as following
1) Oracle Instance is not started.
2) ORACLE_SID or ORACLE_HOME or both are not properly defined.
3) Size of SGA is smaller than an Oracle Instance requires.
4) Remote user might face it due to improper configuration of Listener.
5) Refer to accompanying messages for possible causes and correct the problem.

One of the most common reason for ORA-01034 is Oracle Instance is down. Lets reproduce ORA-01034 by shutting down an Oracle instance and try reconnecting it.

SQL*Plus: Release 11.2.0.3.0 Production on Fri May 23 08:57:00 2014
Copyright (c) 1982, 2011, Oracle.  All rights reserved.
Connected to:
Oracle Database 11g Release 11.2.0.3.0 - Production

SQL> shutdown abort
ORACLE instance shut down.
SQL> exit

C:Usersnimish.garg>sqlplus scott/tiger
SQL*Plus: Release 11.2.0.3.0 Production on Fri May 23 08:57:34 2014
Copyright (c) 1982, 2011, Oracle.  All rights reserved.

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

Related Links:
— ORA-04031: unable to allocate n bytes of shared memory
— ORA-27101: shared memory realm does not exist
— ORA-00600 internal error code
— ORA-01017: invalid username/password; logon denied

Понравилась статья? Поделить с друзьями:
  • Error at line 1 ora 01031 insufficient privileges
  • Error at least one required implicit or forwarded dependency was not found
  • Error at least one file was not a 32 bit or 64 bit windows module
  • Error at initialization of bundled dll ultraactivate dll
  • Error archive data corrupted decompression fails код ошибки 1 windows 10