Home » Server Options » Data Guard » unable to apply the recovery in standby db
unable to apply the recovery in standby db [message #302927] Wed, 27 February 2008 06:34 Go to next message
kesavansundaram
Messages: 183
Registered: October 2007
Location: MUMBAI
Senior Member
 
Dear sir, 



oracle: 9.2.0.6.0

o/s : sunsolaris: 5.9

iam getting flwg error at DR site,

while apply the recovery , iam getting below : 



ORA-00279: change 22610740635 generated at 02/20/2008 12:18:50 needed for

thread 1

ORA-00289: suggestion : /BDPRD_staging/stored_archives/ARC0001_0000066072.arc

ORA-00280: change 22610740635 for thread 1 is in sequence #66072

ORA-00278: log file '/BDPRD_staging/stored_archives/ARC0001_0000066071.arc' no

longer needed for this recovery



===============================================================================

ORA-00283: recovery session canceled due to errors

ORA-01237: cannot extend datafile 139

ORA-01110: data file 139:

'/BDPRD_dbidx/database/BDPRD/index/ACCTING_TAB_INDEX_05_02.dbf'

ORA-19502: write error on file

"/BDPRD_dbidx/database/BDPRD/index/ACCTING_TAB_INDEX_05_02.dbf", blockno

1639169 (blocksize=8192)

ORA-27063: skgfospo: number of bytes read/written is incorrect

SVR4 Error: 28: No space left on device

Additional information: -1

Additional information: 1048576

ORA-19502: write error on file

"/BDPRD_dbidx/database/BDPRD/index/ACCTING_TAB_INDEX_05_02.dbf", blockno

1639041 (blocksize=8192)

ORA-27063: skgfospo: number of bytes read/written is incorrect

Additional information: 172032

Additional information: 1048576

===============================================================================





in this above partition, " /BDPRD_dbidx/database/BDPRD/index/ " 

there are some files.... 





bash-2.05$ cd -

/BDPRD_dbidx/database/BDPRD/index

bash-2.05$ ls -ltr

total 88212912

-rw-r-----   1 oracle92 dba9     1175924500 Feb 25 16:54 ACCTING_TAB_INDEX_05_02.dbf.gz

-rw-r-----   1 oracle92 dba9     536879104 Feb 27 13:26 ACCTING_TAB_INDEX_0705_01.dbf

-rw-r-----   1 oracle92 dba9     2147491840 Feb 27 14:59 PEV_OTHER_INDEX_01.dbf

-rw-r-----   1 oracle92 dba9     1765810176 Feb 27 14:59 MASTER_AUDIT_INDEX_01.dbf

-rw-r-----   1 oracle92 dba9     4294975488 Feb 27 14:59 EXCEPTION_LOG_INDEX_01.dbf

-rw-r-----   1 oracle92 dba9     536879104 Feb 27 14:59 ACCTING_TAB_INDEX_0704_01.dbf

-rw-r-----   1 oracle92 dba9     3221233664 Feb 27 14:59 ACCTING_TAB_INDEX_0702_02.dbf

-rw-r-----   1 oracle92 dba9     6329212928 Feb 27 14:59 ACCTING_TAB_INDEX_05_01.dbf

-rw-r-----   1 oracle92 dba9     2147491840 Feb 27 14:59 ACCTING_TAB_INDEX_04_02.dbf

-rw-r-----   1 oracle92 dba9     1598038016 Feb 27 14:59 ACCTING_TAB_INDEX_0303_01.dbf

-rw-r-----   1 oracle92 dba9     2147491840 Feb 27 14:59 ACCTING_TAB_INDEX_0302_01.dbf

-rw-r-----   1 oracle92 dba9     2147491840 Feb 27 14:59 ACCTING_TAB_INDEX_01_02.dbf

-rw-r-----   1 oracle92 dba9     6356475904 Feb 27 14:59 ACCTING_TAB_INDEX_01_01.dbf

-rw-r-----   1 oracle92 dba9     10737426432 Feb 27 15:01 ACCTING_TAB_INDEX_05_02.dbf <<-subject file in the error 



bash-2.05$





please adv me how to resolve this space issue, 





actually we moved 2 dbf file from abv location to some other location and uupdated in control file as follows: 



alter database rename file 

   '/BDPRD_dbidx/database/BDPRD/index/ACCTING_TAB_INDEX_0705_01.dbf' 

        to '/BDPRD_dbsys/database/BDPRD/data/ACCTING_TAB_INDEX_0705_01.dbf';





alter database rename file '/BDPRD_dbidx/database/BDPRD/index/ACCTING_TAB_INDEX_05_01.dbf' to  '/BDPRD_dbsys/database/BDPRD/data/ACCTING_TAB_INDEX_05_01.dbf';





even then when we apply the recovery this error comes. 

pls adv on urgent basis .



rgds, 

kesavan. 








===============

further, i checked the following: 



SQL> select file#,name,status from v$datafile where file#=139;



     FILE#

----------

NAME

----------------------------------------------------------------------------------------------------

STATUS

-------

       139

/BDPRD_dbidx/database/BDPRD/index/ACCTING_TAB_INDEX_05_02.dbf

RECOVER





SQL>



status shows RECOVER, 

PLS ADV FURTHER. 



TKS/KESAVAN. 



		
		
		
[Updated on: Wed, 27 February 2008 06:42]
Report message to a moderator





	
		
	






	
		

		

			Re: unable to apply the recovery in standby db [message #302929 is a reply to message #302927]
			Wed, 27 February 2008 06:45 Go to previous messageGo to next message
		

		

			
				

				

				
					
						
						NandKumar
						
Messages: 92
Registered: June 2007 
Location: v$hyderabad
						
							
					
Member

					
		

		

			




	
		Seems like you have run out of space in /BDPRD_dbidx mountpoint.



what is the output from df -ah
		
		
		
Report message to a moderator





	
		
	






	
		

		

			Re: unable to apply the recovery in standby db [message #302934 is a reply to message #302929]
			Wed, 27 February 2008 06:56 Go to previous messageGo to next message
		

		

			
				

				

				
					
						
						kesavansundaram
						
Messages: 183
Registered: October 2007 
Location: MUMBAI
						
							
					
Senior Member

					
		

		

			




	
		
there are around 3 gb in that parition...as follows:



bash-2.05$ df -h

Filesystem             size   used  avail capacity  Mounted on

/dev/md/dsk/d0         9.8G   6.4G   3.3G    66%    /

/dev/md/dsk/d3         4.9G   1.6G   3.3G    33%    /usr

/proc                    0K     0K     0K     0%    /proc

mnttab                   0K     0K     0K     0%    /etc/mnttab

fd                       0K     0K     0K     0%    /dev/fd

swap                    21G   112K    21G     1%    /var/run

swap                    21G   640K    21G     1%    /tmp

/dev/dsk/c2t0d2s0       34G    16G    18G    47%    /BDPRD_dbsys

/dev/dsk/c2t0d4s0       71G    61G   9.4G    87%    /BDPRD_dbmain

/dev/dsk/c2t0d2s1      4.9G   835M   4.1G    17%    /BDPRD_dblog

/dev/dsk/c2t0d3s0       54G    51G   2.9G    95%    /BDPRD_dbase

/dev/dsk/c2t0d3s3       49G    45G   3.9G    92%    /BDPRD_dbmain1

/dev/dsk/c2t0d3s1       54G    47G   6.4G    89%    /BDPRD_dbdata1

/dev/dsk/c2t0d3s4       49G    48G   735M    99%    /BDPRD_dbidx1

/dev/dsk/c2t0d4s1       54G    50G   3.8G    93%    /BDPRD_dbdata

/dev/dsk/c2t0d4s3       54G    51G   3.0G    95%    /BDPRD_dbidx

/dev/dsk/c2t0d4s4       54G    49G   4.7G    92%    /BDPRD_dboth

/dev/dsk/c1t2d0s0       30G    29G     0K   100%    /BDPRD_dbarch

/dev/dsk/c1t3d0s2       67G    58G   8.3G    88%    /BDPRD_staging

/dev/dsk/c1t5d0s0       39G    14G    25G    36%    /BDPRD_dbtemp

/dev/dsk/c1t4d0s2       67G    65G   1.3G    99%    /BDPRD_apps

/dev/dsk/c2t0d0s0       25G   4.0G    20G    17%    /PROD_portal

/dev/dsk/c2t0d0s1       25G   4.3G    20G    18%    /PROD_dbmain

/dev/dsk/c1t2d0s1       38G    24G    14G    64%    /home

/dev/md/dsk/d5          20G    14G   5.9G    70%    /oracle

/dev/md/dsk/d4         4.9G    94M   4.8G     2%    /opt












bash-2.05$ df -ah

Filesystem             size   used  avail capacity  Mounted on

/dev/md/dsk/d0         9.8G   6.4G   3.3G    66%    /

/dev/md/dsk/d3         4.9G   1.6G   3.3G    33%    /usr

/proc                    0K     0K     0K     0%    /proc

mnttab                   0K     0K     0K     0%    /etc/mnttab

fd                       0K     0K     0K     0%    /dev/fd

swap                    21G   112K    21G     1%    /var/run

swap                    21G   640K    21G     1%    /tmp

/dev/dsk/c2t0d2s0       34G    18G    16G    55%    /BDPRD_dbsys

/dev/dsk/c2t0d4s0       71G    61G   9.4G    87%    /BDPRD_dbmain

/dev/dsk/c2t0d2s1      4.9G   835M   4.1G    17%    /BDPRD_dblog

/dev/dsk/c2t0d3s0       54G    51G   2.9G    95%    /BDPRD_dbase

/dev/dsk/c2t0d3s3       49G    45G   3.9G    92%    /BDPRD_dbmain1

/dev/dsk/c2t0d3s1       54G    47G   6.4G    89%    /BDPRD_dbdata1

/dev/dsk/c2t0d3s4       49G    48G   735M    99%    /BDPRD_dbidx1

/dev/dsk/c2t0d4s1       54G    50G   3.8G    93%    /BDPRD_dbdata

/dev/dsk/c2t0d4s3       54G    51G   3.0G    95%    /BDPRD_dbidx

/dev/dsk/c2t0d4s4       54G    49G   4.7G    92%    /BDPRD_dboth

/dev/dsk/c1t2d0s0       30G    29G     0K   100%    /BDPRD_dbarch

/dev/dsk/c1t3d0s2       67G    58G   8.3G    88%    /BDPRD_staging

/dev/dsk/c1t5d0s0       39G    14G    25G    36%    /BDPRD_dbtemp

/dev/dsk/c1t4d0s2       67G    65G   1.3G    99%    /BDPRD_apps

/dev/dsk/c2t0d0s0       25G   4.0G    20G    17%    /PROD_portal

/dev/dsk/c2t0d0s1       25G   4.3G    20G    18%    /PROD_dbmain

/dev/dsk/c1t2d0s1       38G    24G    14G    64%    /home

/dev/md/dsk/d5          20G    14G   5.9G    70%    /oracle

/dev/md/dsk/d4         4.9G    94M   4.8G     2%    /opt

-hosts                   0K     0K     0K     0%    /net

-xfn                     0K     0K     0K     0%    /xfn

nfp-sun:vold(pid473)     0K     0K     0K     0%    /vol

bash-2.05$



		
		
		
[Updated on: Wed, 27 February 2008 06:58]
Report message to a moderator





	
		
	






	
		

		

			Re: unable to apply the recovery in standby db [message #302936 is a reply to message #302934]
			Wed, 27 February 2008 07:00 Go to previous messageGo to next message
		

		

			
				

				

				
					
						
						NandKumar
						
Messages: 92
Registered: June 2007 
Location: v$hyderabad
						
							
					
Member

					
		

		

			




	
		See



dev/dsk/c2t0d3s3 49G 45G 3.9G 92% /BDPRD_dbmain1

/dev/dsk/c2t0d3s1 54G 47G 6.4G 89% /BDPRD_dbdata1

/dev/dsk/c2t0d3s4 49G 48G 735M 99% /BDPRD_dbidx1

/dev/dsk/c2t0d4s1 54G 50G 3.8G 93% /BDPRD_dbdata

/dev/dsk/c2t0d4s3 54G 51G 3.0G 95% /BDPRD_dbidx



this is the problem...Its almost filled. Move datafiles in this partition to different partition where enough free space is available






		
		
		
[Updated on: Wed, 27 February 2008 07:00]
Report message to a moderator





	
		
	






	
		

		

			Re: unable to apply the recovery in standby db [message #302944 is a reply to message #302936]
			Wed, 27 February 2008 07:18 Go to previous messageGo to next message
		

		

			
				

				

				
					
						
						kesavansundaram
						
Messages: 183
Registered: October 2007 
Location: MUMBAI
						
							
					
Senior Member

					
		

		

			




	
		
pls cfm once again, 

my concerned data files is in partition: 

/BDPRD_dbidx/database/BDPRD/index/ACCTING_TAB_INDEX_05_02.dbf



not in BDPRD_dbidx1....



PLS CFM ONCE AGAIN, I MOVE IT IMMEDLY



THK YOU



		
		
		
Report message to a moderator





	
		
	






	
		

		

			Re: unable to apply the recovery in standby db [message #302946 is a reply to message #302936]
			Wed, 27 February 2008 07:20 Go to previous messageGo to next message
		

		

			
				

				

				
					
						
						NandKumar
						
Messages: 92
Registered: June 2007 
Location: v$hyderabad
						
							
					
Member

					
		

		

			




	
		OK, i noticed.

 
		
		
		
Report message to a moderator





	
		
	






	
		

		

			Re: unable to apply the recovery in standby db [message #302947 is a reply to message #302936]
			Wed, 27 February 2008 07:20 Go to previous messageGo to next message
		

		

			
				

				

				
					
						
						kesavansundaram
						
Messages: 183
Registered: October 2007 
Location: MUMBAI
						
							
					
Senior Member

					
		

		

			




	
		
NANDAKUMAR, 

THE PROB SOLVED,

I MOVED THE SUBJECT FILE FROM IDX PARTITION TO SOME OTHER 

PARTITION, NOW ARCH FILES ARE GETTING APPLIED..

THANK YOU VERY MUCH .

		
		
		
Report message to a moderator





	
		
	






	
		

		

			Re: unable to apply the recovery in standby db [message #302952 is a reply to message #302947]
			Wed, 27 February 2008 07:25 Go to previous message
		

		

			
				

				

				
					
						
						NandKumar
						
Messages: 92
Registered: June 2007 
Location: v$hyderabad
						
							
					
Member

					
		

		

			




	
		Felt happy to hear that.




		
		
		
Report message to a moderator





	
		
	












	

	Previous Topic:
	log_sequence column in v$archive_dest


	

	Next Topic:
	Creating StandBy Database





Goto Forum:


	
	
	  
	





[ Syndicate this forum (XML) ] [ RSS ] 


Current Time: Tue Apr 16 14:34:32 CDT 2024









	.::
	Forum Home ::
	Blogger Home ::
	Wiki Home ::
	Contact ::
	Privacy
	::.