Environment information:
* Oracle version: 9.2.0.1.0
* Operating system: WinXP
Good afternoon guys ... I'm facing a problem here, I have a network micro that connects to the banks of the served normally. I installed it in the same version of the bank that is on the server, I configured the files of tnsnames, everything beauty .... the bank was connecting everything right, only one hour to another after restarting the computer I can only connect with the SQL -Plus (MS-DOS), nor oracle sql-plus * ferment does not connect ... the worst is that no error message, just locks ....
already passed by iso or have some idea of ??what can be ....
already tried to reconfigure the lister (net configuration) but he also hangs ...
I can not connect to the database
I already solved ... I deleted the lister and includes again ... it was kind of kick ... but thanks for the attention ...
Now I'm facing a message of the type
This is not with a good face ... Rs Someone know what can be done?
Abrçs
Now I'm facing a message of the type
ORA-00257: archiver error. Connect internal only, until freed.
Abrçs
Galera, I have a local bank that is mirror than I have on the server, I had to restart my micro because the same had caught, the other day when I tried to connect in the SQL * plus gave the sequise message:
What error is this and how can I solve.
Thank you in advance.
ERROR:
ORA-01033: ORACLE initialization or shutdown in progress"
Tentei fazer o seguinte procedimento:
SQL> connect / as sysdba
Conectado.
SQL> shutdown
ORA-01109: banco de dados não aberto
Banco de dados desmontado.
Instância ORACLE desativada.
SQL> startup
Instância ORACLE iniciada.
Total System Global Area 167772160 bytes
Fixed Size 1247900 bytes
Variable Size 83887460 bytes
Database Buffers 79691776 bytes
Redo Buffers 2945024 bytes
Banco de dados montado.
Então ele me retorna o erro:
ORA-00600: código de erro interno, argumentos: [kcratr1_lastbwr], [], [], [],
[], [], [], []
Thank you in advance.
-
- Rank: Analista Sênior
- Posts: 153
- Joined: Thu, 01 Nov 2007 2:53 pm
- Location: Osasco
Eli Dias
Oracle Certified Professional
Oracle Certified Professional
Good afternoon,
When generic errors happens this way it is difficult to view, the cool would be to enter the metalink site for verification.
Only one thing, at Alert.log Is no other message your message with this, in the moment you realize the instance startup?
Hugs,
When generic errors happens this way it is difficult to view, the cool would be to enter the metalink site for verification.
Only one thing, at Alert.log Is no other message your message with this, in the moment you realize the instance startup?
Hugs,
-
- Rank: Estagiário Júnior
- Posts: 2
- Joined: Tue, 15 Mar 2011 8:48 am
- Location: Brasília - DF
Oproblem happened to me yesterday.:
First, check the Alert and Trace files to discover the real problem:
In my case, it was the files that specify the limit size for the Flash Recovery Area, they had burst the limit
to resolve, it has to check the size available in the Arch Logs.
Available limit:
Location Where is being stored:
or You change location or increases the file size
move them to a new location - in my case using the ASM:
log_archive_dest_1: This parameter defines The location that the Archive Logs will be created.
or
change the size of the File:
db_recovery_file_dest_size: Specifies the limit size for the Flash Recovery Area Manage RMAN-made backups, for example, you can set a maximum storage value that the area will maintain.
Finally, do the redolols switch and the filing of the same.:
more or less it there!
@ thisombra hug to all !!
ORA-00257: archiver error. Connect internal only, until freed tips,
show parameter background_dump_dest;
to resolve, it has to check the size available in the Arch Logs.
Available limit:
SELECT * FROM V$RECOVERY_FILE_DEST;
Location Where is being stored:
show parameter log_archive_dest
move them to a new location - in my case using the ASM:
log_archive_dest_1: This parameter defines The location that the Archive Logs will be created.
alter system set LOG_ARCHIVE_DEST_1='location=+DG_DATA2/';
or
alter system set LOG_ARCHIVE_DEST_1='location=/u01/oradata/MYSID/archive/';
change the size of the File:
db_recovery_file_dest_size: Specifies the limit size for the Flash Recovery Area Manage RMAN-made backups, for example, you can set a maximum storage value that the area will maintain.
ALTER SYSTEM SET db_recovery_file_dest_size='10G' SCOPE=BOTH;
ALTER SYSTEM SWITCH LOGFILE;
ALTER SYSTEM ARCHIVE LOG ALL;
@ thisombra hug to all !!
-
- Information
-
Who is online
Users browsing this forum: No registered users and 8 guests