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:)))

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:)))

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:)))

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

ERROR: NMO not setuid-root

When using Enterprise Manager, you might get the following error message:
If you get this error while using Enterprise Manager;

Problem:ERROR: NMO not setuid-root (Unix-only)

Solution:

$ su - root

$ cd $ORACLE_HOME/bin

$ chown root nmb nmhs nmo

$ chmod 6750 nmb nmhs nmo

Then restart the database:)

ORA-04031:unable to allocate 248 bytes of shared memory

Problem:ORA-04031:unable to allocate 248 bytes of shared memory

Solution:If we get this error,we have to open our parameter file init.ora.End then increase below parameters

**shared_pool_reserved_size

**shared_pool_size

**SGA 

After we increased these parameters shutdown your application,shutdown your database,startup your database,startup your application.

Note:If you don't have application just shutdown database then startup your database:))))

adstpall.sh:Exiting with status 1

Problem:For shut down your ERP application you have to run this below script

While shutting down your application you may get this error.


------------------------------------------------------------------------------------------------------
You are running adstpall.sh version 120.10.12010000.4


Enter the APPS username: apps

Enter the APPS password:

file:/u01/test_appl/inst/apps/doganay_erpdb/appl/admin/doganay_erpdb.xml<Line 2, Column 6>: XML-20109: (Fatal Error) PI with the name 'xml' can occur only in the beginning of the document.
The logfile for this session is located at /u01/test_appl/inst/apps/doganay_erpdb/logs/appl/admin/log/adstpall.log
Exception in thread "main" java.lang.NullPointerException
        at oracle.apps.ad.autoconfig.ServiceControl.parseServices(ServiceControl.java:487)
        at oracle.apps.ad.autoconfig.ServiceControl.<init>(ServiceControl.java:331)
        at oracle.apps.ad.autoconfig.ServiceControl.main(ServiceControl.java:976)

adstpall.sh:Exiting with status 1

adstpall.sh:  check the logfile /u01/test_appl/inst/apps/doganay_erpdb/logs/appl/admin/log/adstpall.log for more information



/u01/test_appl/inst/apps/doganay_erpdb/appl/admin/doganay_erpdb.xml

--------------------------------------------------------------------------------------------------------
Solution:You may have damaged your doganay_erpdb.xml file.You have to back your doganay_erpdb.xml backup.

If we recovery your doganay_erpdb.xml backup,application will shutdown smoothly:)))