CASE 1 resolved
1. When you call the report the report runtime hangs and show this error.
2. if you copy the function table to the sqlplus and execution using the same parameters, you get disconnected.3. The way we solved the problem, was modifying two times (adding a null; recompile, adding another null; and recompile)
4. execute from sqlplus and don't get disconnect.
5. execute the report and the error dissapear.
CASE 2 unresolved
1. When you call the report the report runtime hangs and show this error.
2. if you copy the function table to the sqlplus and execution using the same parameters, you DON'T get disconnected.
3. You can recreate the report, or as we do recreate the report in jasper, because we are migrating our reports, from oracle reports 6i.
lunes, 6 de julio de 2015
martes, 16 de junio de 2015
Use (ROW_NUMBER() OVER( ORDER BY xxx) instead of ROWNUM in query as a value
The reason for not using rownum as a value is because when you use in an insert, the value can be different than in a select using an order by clause.
but if you use analytic functions the problem is solved
(ROW_NUMBER() OVER( ORDER BY xxx)
but if you use analytic functions the problem is solved
(ROW_NUMBER() OVER( ORDER BY xxx)
jueves, 21 de mayo de 2015
ntldr is missing in windows 8.1
Starting in repair mode
C:\WINDOWS\system32>bootsect /nt60 C:
Se actualizarán los volúmenes de destino con el código de arranque compatible BOOTMGR.
C: (\\?\Volume{b45168bf-6f54-11e4-8253-005056c00008})
Código de arranque del sistema de archivos NTFS actualizado.
Es posible que la actualización no sea confiable ya que el
volumen no se pudo bloquear durante la actualización:
Acceso denegado.
Se actualizó correctamente el código de arranque en todos los volúmenes de destino.
C:\WINDOWS\system32>
C:\WINDOWS\system32>bootsect /nt60 C:
Se actualizarán los volúmenes de destino con el código de arranque compatible BOOTMGR.
C: (\\?\Volume{b45168bf-6f54-11e4-8253-005056c00008})
Código de arranque del sistema de archivos NTFS actualizado.
Es posible que la actualización no sea confiable ya que el
volumen no se pudo bloquear durante la actualización:
Acceso denegado.
Se actualizó correctamente el código de arranque en todos los volúmenes de destino.
C:\WINDOWS\system32>
miércoles, 13 de mayo de 2015
expdp error -3212 temporary segment cannot be creaetd in locally managed tablespace
This problem happened in an enterprise test database , when exporting to standard edition.
Note www is a non oracle default user.
SET NLS_DATE_FORMAT=YYYY/MM/DD HH24:MI:SS
c:\app\11gent\product\11.2.0\dbhome_1\bin\expdp www/yyyy@xxx full=Y directory=EXPDP dumpfile=EXPPERP_11G.dmp logfile=expdpPERP.log METRICS=Y exclude=statistics
ORA-39006: internal error
ORA-39065: unexpected master process exception in DISPATCH
ORA-03212: Temporary Segment cannot be created in locally-managed tablespace
ORA-39097: Data Pump job encountered unexpected error -3212
SOLUTION: changed the user www to system and everything ok
c:\app\11gent\product\11.2.0\dbhome_1\bin\expdp SYSTEM/yyyy@xxx full=Y directory=EXPDP dumpfile=EXPPERP_11G.dmp logfile=expdpPERP.log METRICS=Y exclude=statistics
Note www is a non oracle default user.
SET NLS_DATE_FORMAT=YYYY/MM/DD HH24:MI:SS
c:\app\11gent\product\11.2.0\dbhome_1\bin\expdp www/yyyy@xxx full=Y directory=EXPDP dumpfile=EXPPERP_11G.dmp logfile=expdpPERP.log METRICS=Y exclude=statistics
ORA-39006: internal error
ORA-39065: unexpected master process exception in DISPATCH
ORA-03212: Temporary Segment cannot be created in locally-managed tablespace
ORA-39097: Data Pump job encountered unexpected error -3212
SOLUTION: changed the user www to system and everything ok
c:\app\11gent\product\11.2.0\dbhome_1\bin\expdp SYSTEM/yyyy@xxx full=Y directory=EXPDP dumpfile=EXPPERP_11G.dmp logfile=expdpPERP.log METRICS=Y exclude=statistics
martes, 20 de enero de 2015
recreating idl_ub1$ idl_char$ idl_ub2$ and idl_sb4$ caused by corruption in 11g
RMAN couldn't backup the database because there was corruption in one of this tables.
CHECK IN A TEST DATABASE FIRST!!!
This is how we fixed corruption in this sys tables, and worked.
SQLPLUS /NOLOG
CONN SYS@db AS SYSDBA
shutdown immediate
startup upgrade
truncate table idl_ub1$;
truncate table idl_char$;
truncate table idl_ub2$;
truncate table idl_sb4$;
@c:\oracle\product\10.2.0\db_1\rdbms\admin\utlirp
shutdown immediate
startup upgrade
@c:\oracle\product\10.2.0\db_1\javavm\install\rmjvm
shutdown immediate
exit
SQLPLUS /NOLOG
CONN SYS@db AS SYSDBA
shutdown immediate
startup upgrade
alter system set "_system_trig_enabled"=false scope=memory;
@c:\oracle\product\10.2.0\db_1\javavm\install\initjvm.sql
-- if you have xml installed
@c:\oracle\product\10.2.0\db_1\xdk\admin\initxml.sql
@c:\oracle\product\10.2.0\db_1\xdk\admin\xmlja.sql
@c:\oracle\product\10.2.0\db_1\rdbms\admin\catjava.sql
--
shutdown immediate
exit
SQLPLUS /NOLOG
CONN SYS@db AS SYSDBA
shutdown immediate
startup upgrade
@c:\oracle\product\10.2.0\db_1\rdbms\admin\utlrp
exit
** reiniciar servicio
** reiniciar servicio
** reiniciar servicio
SQLPLUS /NOLOG
CONN SYS@db AS SYSDBA
shutdown immediate
startup
execute utl_recomp.recomp_serial();
exit
-- prueba de fullbackup
RMAN
connect target SYS@db
CHECK IN A TEST DATABASE FIRST!!!
This is how we fixed corruption in this sys tables, and worked.
SQLPLUS /NOLOG
CONN SYS@db AS SYSDBA
shutdown immediate
startup upgrade
truncate table idl_ub1$;
truncate table idl_char$;
truncate table idl_ub2$;
truncate table idl_sb4$;
@c:\oracle\product\10.2.0\db_1\rdbms\admin\utlirp
shutdown immediate
startup upgrade
@c:\oracle\product\10.2.0\db_1\javavm\install\rmjvm
shutdown immediate
exit
SQLPLUS /NOLOG
CONN SYS@db AS SYSDBA
shutdown immediate
startup upgrade
alter system set "_system_trig_enabled"=false scope=memory;
@c:\oracle\product\10.2.0\db_1\javavm\install\initjvm.sql
-- if you have xml installed
@c:\oracle\product\10.2.0\db_1\xdk\admin\initxml.sql
@c:\oracle\product\10.2.0\db_1\xdk\admin\xmlja.sql
@c:\oracle\product\10.2.0\db_1\rdbms\admin\catjava.sql
--
shutdown immediate
exit
SQLPLUS /NOLOG
CONN SYS@db AS SYSDBA
shutdown immediate
startup upgrade
@c:\oracle\product\10.2.0\db_1\rdbms\admin\utlrp
exit
** reiniciar servicio
** reiniciar servicio
** reiniciar servicio
SQLPLUS /NOLOG
CONN SYS@db AS SYSDBA
shutdown immediate
startup
execute utl_recomp.recomp_serial();
exit
-- prueba de fullbackup
RMAN
connect target SYS@db
miércoles, 23 de julio de 2014
How to restore rman database backup on Oracle 9i
If you have two archives one of controlfiles and another of the database
rman NOCATALOG
CONNECT TARGET user/password@bd
SHUTDOWN IMMEDIATE
STARTUP NOMOUNT
RESTORE CONTROLFILE FROM 'D:\XXX\yyy.bk';
ALTER DATABASE MOUNT
-- execute this query and see where are the backuppieces stored
SELECT * FROM V$BACKUP_PIECE
--copy to that location the archive peice, and send the restore
restore database check readonly;
alter database open resetlogs;
rman NOCATALOG
CONNECT TARGET user/password@bd
SHUTDOWN IMMEDIATE
STARTUP NOMOUNT
RESTORE CONTROLFILE FROM 'D:\XXX\yyy.bk';
ALTER DATABASE MOUNT
-- execute this query and see where are the backuppieces stored
SELECT * FROM V$BACKUP_PIECE
--copy to that location the archive peice, and send the restore
restore database check readonly;
alter database open resetlogs;
miércoles, 30 de abril de 2014
http://sourceforge.net/projects/symphonic/ alternative for Sony sonic stage
Sony SonicStage 4.3 alternative It work, tested :).
This projects gives the same functionality that Sony SonicStage 4.3
http://sourceforge.net/projects/symphonic/
This projects gives the same functionality that Sony SonicStage 4.3
http://sourceforge.net/projects/symphonic/
Suscribirse a:
Entradas (Atom)