I don't want you to mail me directly; pose the question to Lazydba discussion forum !
Anyway, you have defined a rollback segment with a maxextents clause, and this upper limit has been reached; however, the transaction wants to write more undo info to this rollback segment.
Solution : raise the maxextents limit on this rollback segment.
e.g.
SQL> alter rollback segment XXXXX storage (maxextents 3000);
or
SQL> alter rollback segment XXXXX storage (maxextents unlimited);
Hans
-----Original Message-----
From: PAVAN KUMAR T [mailto:[Email address protected]
Sent: vrijdag 6 oktober 2006 12:14
To: Wijte, J.F. (Hans)
Subject: How to solve this error
**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
We have two production boxses, while creating ROLLBACK SEGMENT in one box it is fine but in other box it is throwing this type of error such as the number is ora-01562 and 01628 .My prod server is in oracle 8i pls give the solution it is urgent
Thanks & Regards ____________________
T.Pavan Kumar
Oracle Database Administrator
-----Original Message-----
From: Hans [Email address protected]
Sent: Thursday, October 05, 2006 10:55 AM
To: LazyDBA Discussion
Subject: RE: view
If you have set this parameter to the wrong value (i.e. to timestamp), then the repercussions can be large;
The parameter dictates the behaviour and dependency of PL/SQL objects in your database in relation to remote objects (objects in another database), i.e. it specifies how dependencies upon remote stored procedures are to be handled by the database.
If this parameter is set to TIMESTAMP, which is the default setting, the client running the procedure compares the timestamp recorded on the server side procedure with the current timestamp of the local procedure and executes the procedure only if the timestamps match; this can result in you having to recompile a lot of objects
If the parameter is set to SIGNATURE, the procedure is allowed to execute as long as the signatures are considered safe. This allows client PL/SQL applications to be run without recompilation.
Hans
-----Original Message-----
From: Sood Ankit (GE Money consultant) [mailto:oracledba-ezmlmshield-x82371447.[Email address protected]
Sent: donderdag 5 oktober 2006 4:41
To: LazyDBA Discussion
Subject: view
Hi all,
What is the significance of REMOTE_DEPENDENCIES_MODE
Regards,
Ankit
---------------------------------------------------------------------
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
-----------------------------------------------------------------
ATTENTION:
The information in this electronic mail message is private and confidential, and only intended for the addressee. Should you receive this message by mistake, you are hereby notified that any disclosure, reproduction, distribution or use of this message is strictly prohibited. Please inform the sender by reply transmission and delete the message without copying or opening it.
Messages and attachments are scanned for all viruses known.
If this message contains password-protected attachments, the files have NOT been scanned for viruses by the ING mail domain. Always scan attachments before opening them.
-----------------------------------------------------------------
---------------------------------------------------------------------
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.techmahindra.com/Disclaimer.html</a> externally and <a href="http://tim.techmahindra.com/Disclaimer.html">http://tim.techmahindra.com/Disclaimer.html</a> internally within Tech Mahindra.
============================================================================================================================
-----------------------------------------------------------------
ATTENTION:
The information in this electronic mail message is private and
confidential, and only intended for the addressee. Should you
receive this message by mistake, you are hereby notified that
any disclosure, reproduction, distribution or use of this
message is strictly prohibited. Please inform the sender by
reply transmission and delete the message without copying or
opening it.
Messages and attachments are scanned for all viruses known.
If this message contains password-protected attachments, the
files have NOT been scanned for viruses by the ING mail domain.
Always scan attachments before opening them.
-----------------------------------------------------------------
Oracle LazyDBA home page