RE: Why we get these errors - urgent - please!

RE: Why we get these errors - urgent - please!

 

  

These errors occur because of some EXTENT ISSUE,

ORA-01562 failed to extend rollback segment number string

Cause: Failure occurred when trying to extend rollback segment.
Action: This is normally followed by another error message that caused
the failure. You may take the rollback segment offline to perform
maintenance. Use SELECT SEGMENT_NAME FROM DBA_ROLLBACK_SEGS WHERE
SEGMENT_ID=string (where string is the segment number from the message)
to determine the rollback segment name. Then use the ALTER ROLLBACK
SEGMENT OFFLINE command to take the rollback segment offline.


ORA-01628 max # extents (string) reached for rollback segment string

Cause: An attempt was made to extend a rollback segment that was already
at the MAXEXENTS value.
Action: If the value of the MAXEXTENTS storage parameter is less than
the maximum allowed by the system, raise this value.

Karthik

-----Original Message-----
From: PAVAN KUMAR T [mailto:[Email address protected]
Sent: Friday, October 06, 2006 11:19 AM
To: KARTHIK.[Email address protected]
Subject: Why we get these errors - urgent - please!

**A LazyDBA.com subscriber has responded to your lazydba.com post**
**LazyDBA.com mail shield has forwarded you this email,
**and removed any attachments, and kept your email address secret
**from this person, and any viruses/trojans.
**If you reply to this email, the person will see your email address as
normal
**Anything below this line is the original email text



Hi all
ora-01562 and 01628




Thanks & Regards ____________________


T.Pavan Kumar
Oracle Database Administrator

Tech Mahindra, 4th Floor Annex | Pune

Gold Mine - (ASG)

Ph. (+91) 6609 7200 x-8075

___________________________________

-----Original Message-----
From: karthik ganesan
[Email address protected]

Sent: Thursday, October 05, 2006 9:27 AM
To: LazyDBA Discussion
Subject: Regarding RMAN restoration - urgent - please!

Hi all,


I'm using oracle RMAN for hot backup and recovery, its working fine.


My current practice-
I take the RMAN hot backup every night and then restore the contents on
another server. During this phase the ATM machine won't be accessible
due to resource crunching that takes place because of hot backup.


My proposed view -
Once the data is restored, take the archive logs every 2 hours and just
keep running, Recover database; The advantage, I need not take hot
backup every night in the Live, instead transfer only the archive logs
and apply it on the backup server database. When situation demands use
ALTER DATABASE OPEN RESETLOGS;


Will there be any flaw or data inconsistency will it occur?


Regards,
KARTHIK GANESAN
IT Consultant
Uganda







---------------------------------------------------------------------
TO REPLY TO EVERYBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY To post a
dba job: http://jobs.lazydba.com To Subscribe : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html



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

Tech Mahindra, formerly Mahindra-British Telecom.


Disclaimer:

This message and the information contained herein is proprietary and
confidential and subject to the Tech Mahindra policy statement, you may
review at <a
href="http://www.techmahindra.com/Disclaimer.html">http://www.techmahind
ra.com/Disclaimer.html</a> externally and <a
href="http://tim.techmahindra.com/Disclaimer.html">http://tim.techmahind
ra.com/Disclaimer.html</a> internally within Tech Mahindra.

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




Oracle LazyDBA home page