29 Haziran 2012 Cuma
RMAN-03009: failure of backup command on ORA_DISK_1 channel
Hi,
I was getting backup application's database,I got these errors in below.
Master problem is;
ORA-19566: exceeded limit of 0 corrupt blocks for file /u01/test_db/sys/system09.dbf
We use E-Business Suite R12,so we have a lot of system dbf.
Problem:
channel ORA_DISK_1: starting piece 1 at 29-JUN-12
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 06/29/2012 10:20:22
ORA-19566: exceeded limit of 0 corrupt blocks for file /u01/test_db/sys/system09.dbf
continuing other job steps, job failed will not be re-run
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
including current control file in backup set
channel ORA_DISK_1: starting piece 1 at 29-JUN-12
channel ORA_DISK_1: finished piece 1 at 29-JUN-12
piece handle=/u01/backup/NECOTEST_787227623_42.rman tag=TAG20120629T101617 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 06/29/2012 10:20:22
ORA-19566: exceeded limit of 0 corrupt blocks for file /u01/test_db/sys/system09.dbf
Solution:
SQL> select file_name,tablespace_name,bytes/1024/1024/1024 from dba_data_files where tablespace_name='SYSTEM';
FILE_NAME
--------------------------------------------------------------------------------
TABLESPACE_NAME BYTES/1024/1024/1024
------------------------------ --------------------
/u01/test_db/sys/system09.dbf
SYSTEM 1.46484375
/u01/test_db/sys/system08.dbf
SYSTEM 1.7578125
/u01/test_db/sys/system07.dbf
SYSTEM .732421875
Our system09.dbf is 1,46 GB.We will change this dbf size then return old size.
SQL> alter database datafile '/u01/test_db/sys/system09.dbf' resize 1000m
Then;
SQL> alter database datafile '/u01/test_db/sys/system09.dbf' resize 1464m
After this changes
We can take backup successfully...
Have a nice weekend:)))
28 Haziran 2012 Perşembe
Display Netbackup Admin Console on Solaris
Hi,
I installed Symantec Netbackup 7.5 on Solaris 10_SPARC(64 bit) server.This server is
master server.Then I wanted to open Admin console on vnc to configure client server
admin console path=/usr/openv/netbackup/bin/./jnbSA
But it didn't work,can't display anything.I searched internet and tried all of
method,but I didn't find any solution.
Then my friend that the admin of 'howto.gen.tr',suggest a program to open netbackup
admin konsole.This program name is XMANAGER.
XMANAGER uses ssh(port 22),also vnc uses ssh(port 22).XMANAGER connect directly;
but vnc opens a port.
Good luck:)))
21 Haziran 2012 Perşembe
FRM-92101: There was a failure in the Forms Server during stratup.
Problem:If you run the form you may get this error
FRM-92101: There was a failure in the Forms Server during stratup.
Solution:Download openmotif21-2.1.30-11.EL5.i386.rpm from
http://oss.oracle.com/projects/compat-oracle/files/Enterprise_Linux/
then
#rpm -ivh openmotif21-2.1.30-11.EL5.i386.rpm
Good luck:)))
7 Haziran 2012 Perşembe
You have encountered an unexpected error. Please contact the System Administrator for assistance.
Hi,
While you're logging in e-business suite erp web page(just;erpdb.doganay.com.tr)
You may get this error :
Error Page
----------------------------
You have encountered an unexpected error. Please contact the System Administrator for assistance.
Don't panic:)))
Apache,web server or application cache may caused this error.But before the searching these things from the metalink.I advice 'bounce the server':))
Solution:Stop the application and start the application
While you're logging in e-business suite erp web page(just;erpdb.doganay.com.tr)
You may get this error :
Error Page
----------------------------
You have encountered an unexpected error. Please contact the System Administrator for assistance.
Don't panic:)))
Apache,web server or application cache may caused this error.But before the searching these things from the metalink.I advice 'bounce the server':))
Solution:Stop the application and start the application
Kaydol:
Kayıtlar (Atom)