viernes, 6 de julio de 2018

ORA-12638: Credential retrieval failed SOLVED SQLNET.ORA

IN SQLNET.ORA change SQLNET.AUTHENTICATION_SERVICES

SQLNET.AUTHENTICATION_SERVICES=(NONE)
#SQLNET.AUTHENTICATION_SERVICES=(NTS)

jueves, 28 de junio de 2018

sql developer 00604 12705 solved No se puede acceder a los archivos de datos NLS

Se ha producido un error al realizar la operación solicitada:

ORA-00604: se ha producido un error a nivel 1 de SQL recursivo
ORA-12705: No se puede acceder a los archivos de datos NLS o se ha especificado un entorno no válido
00604. 00000 -  "error occurred at recursive SQL level %s"
*Cause:    An error occurred while processing a recursive SQL statement
           (a statement applying to internal dictionary tables).
*Action:   If the situation described in the next error on the stack
           can be corrected, do so; otherwise contact Oracle Support.
Código de proveedor 604

sqldeveloper\sqldeveloper\bin\sqldeveloper.conf

add lines
AddVMOption  -Duser.region=us
AddVMOption  -Duser.language=en

martes, 22 de mayo de 2018

ORA-38802: ORA-02063: Edition doesn't exists, having only one edition through database link

I only have one edition

select * from dba_editions;
ORA$BASE          YES

It is the default edition
SELECT property_value
FROM   database_properties
WHERE  property_name = 'DEFAULT_EDITION';
ORA$BASE
 
making a select through a database link
select * from dual@database_with_problem.world 
I starting to get the error: 
 
ORA-38802: Edition does not exists
ORA-02063: 

I executed the command:
ALTER DATABASE DEFAULT EDITION = ORA$BASE;
 
And it get solved, magically.

 

miércoles, 28 de marzo de 2018

After renaming database ORA-00604: error occurred at recursive SQL level 2

ERROR at line 1:
ORA-00604: error occurred at recursive SQL level 2
ORA-25153: Temporary Tablespace is Empty

You have to disable database triggers, before renaming, or after recreating the database.

SHUTDOWN IMMEDIATE
 STARTUP UPGRADE ;

SELECT 'ALTER TRIGGER '||OWNER||'.'||TRIGGER_NAME||' DISABLE;' FROM DBA_TRIGGERS WHERE base_object_type LIKE '%DATABASE%';

viernes, 8 de diciembre de 2017

ORA-12224 connection forms 6i with oracle database 12c

used ip insteaad of name and it got fixed, why?
No idea.

BBBV_3_17.WORLD=(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=jreyes)(PORT=1522))(CONNECT_DATA=(SID=BBBV)))
BBBV_3_17.WORLD=(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.3.17)(PORT=1522))(CONNECT_DATA=(SID=BBBV)))

miércoles, 6 de diciembre de 2017

upgrading 12.2 preupgrade.jar ORA-01017

SET ORACLE_SID=BBBV
SET ORACLE_BASE=c:\app\jreyes
SET ORACLE_HOME=C:\app\jreyes\product\12.1.0.1.13\dbhome_1

C:\app\jreyes\product\11.2.0\dbhome_1\jdk\bin\java -jar C:\app\product\12.2.0\dbhome_1\rdbms\admin\preupgrade.jar FILE TEXT DIR D:\TEMPD

ERROR - Unable to run sqlplus due to:
ORA-01017:
SP2-0751: Unable to connect to Oracle.  Exiting SQL*Plus


Solution:
I ran
C:\app\product\12.2.0\dbhome_1\bin\launch.exe c:\app\product\12.2.0\dbhome_1\bin dbua.cl
and I run from the wizard the preupgrade check and it worked.