01-24-2011
Hi, If you commited what you had before applying the tl and you only applied the tl over the commited info, you can just reject applied software and go back to the state before applying the fixes.
Regards.
Pablo
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi all,
Have a small problem.
Back in October the pervious sys-admin (of a client's company) made the necessary adjustments to the system clock for daylight savings (Sydney time - +11 GMT).
As far as I can gather, they just amended the time - NO TIMEZONE !?!
Is there an effective and safe... (5 Replies)
Discussion started by: Cameron
5 Replies
2. AIX
Hello, I recently did an update from 5300-0-0 to 5300-05-06. When I run lppchk -v I get the following errors:
# lppchk -v
lppchk: The following filesets need to be installed or corrected to bring
the system to a consistent state:
invscout.rte 2.1.0.0 (not... (4 Replies)
Discussion started by: dkranes
4 Replies
3. AIX
Hi Guys
I am currently running AIX 5.3 technology level 6 on a 570, but want to go up to level 9.
However I am struggling to find on IBM's website the new features that it brings in, along with the commands for these new features.
Can any one help me with this?
Thanks (7 Replies)
Discussion started by: ryanbsc@gmail.c
7 Replies
4. AIX
Hello. Im attempting to install Oracle 11g, but my current AIX is a bit too old. Oracle 11g require TV 5300-05-06, and my current AIX TV is:
% oslevel -s
5300-05-00
So what would be the best way to update TV? Thanks. (6 Replies)
Discussion started by: bsddaemon
6 Replies
5. AIX
Hello
I update one lpar from TL03 to TL06 reboot and check with lppchk -v, errpt and everything looks fine then I commit my fileset and I update to TL08-04.
The installation was ok. I reboot my machine again check with lppchk -v and errpt and its ok, but when I type oslevel -s I get this... (5 Replies)
Discussion started by: lo-lp-kl
5 Replies
6. AIX
Dont know what happened, my AIX 53 TL6 os just reverted back to original TL4 from whence I started this week. Is there a commad to check the ODM or kernel or something to ensure stability? (2 Replies)
Discussion started by: mrmurdock
2 Replies
7. Linux
I am writing a software product and hope that it will work on a variety of Linux distributions. At the moment, I am trying to create some kind of Linux version of patches/upgrades of installed software. Gathering information on available updates isn't hard, nor is installation of updates, but I... (27 Replies)
Discussion started by: Brandon9000
27 Replies
8. UNIX for Dummies Questions & Answers
Can some one help me related to .sql file issue.
I have a .sqlfile and tried to read the file thru unix. In the .sqlfile I have error rows as well and when error comes I dont want to proceed further and need to roll back all the transactions.
sample .sql file below
insert into
test... (2 Replies)
Discussion started by: sri_aue
2 Replies
9. Shell Programming and Scripting
Hi Agian
Sorry for all these questions...:
Last one for a whie, I promise
This is an example of a menu script I am using. It works OK...when I get to the 2nd menu level, if the command is issued or canceled, I would like to go back to the first menu (# MAIN SECTION)
This is NOT the... (7 Replies)
Discussion started by: olearydc
7 Replies
10. AIX
Hello,
I was trying to upgrade TL on a lab server (test box). I did worked on (few) these type of SP and TL updates in the recent past. I saw the below message for the first time on server.
current OS level : 7100-03-01-1341
downloaded the newest/recent fix pack from fix central as... (3 Replies)
Discussion started by: system.engineer
3 Replies
LEARN ABOUT CENTOS
rollback_to_savepoint
ROLLBACK TO
SAVEPOINT(7) PostgreSQL 9.2.7 Documentation ROLLBACK TO SAVEPOINT(7)
NAME
ROLLBACK_TO_SAVEPOINT - roll back to a savepoint
SYNOPSIS
ROLLBACK [ WORK | TRANSACTION ] TO [ SAVEPOINT ] savepoint_name
DESCRIPTION
Roll back all commands that were executed after the savepoint was established. The savepoint remains valid and can be rolled back to again
later, if needed.
ROLLBACK TO SAVEPOINT implicitly destroys all savepoints that were established after the named savepoint.
PARAMETERS
savepoint_name
The savepoint to roll back to.
NOTES
Use RELEASE SAVEPOINT (RELEASE_SAVEPOINT(7)) to destroy a savepoint without discarding the effects of commands executed after it was
established.
Specifying a savepoint name that has not been established is an error.
Cursors have somewhat non-transactional behavior with respect to savepoints. Any cursor that is opened inside a savepoint will be closed
when the savepoint is rolled back. If a previously opened cursor is affected by a FETCH or MOVE command inside a savepoint that is later
rolled back, the cursor remains at the position that FETCH left it pointing to (that is, the cursor motion caused by FETCH is not rolled
back). Closing a cursor is not undone by rolling back, either. However, other side-effects caused by the cursor's query (such as
side-effects of volatile functions called by the query) are rolled back if they occur during a savepoint that is later rolled back. A
cursor whose execution causes a transaction to abort is put in a cannot-execute state, so while the transaction can be restored using
ROLLBACK TO SAVEPOINT, the cursor can no longer be used.
EXAMPLES
To undo the effects of the commands executed after my_savepoint was established:
ROLLBACK TO SAVEPOINT my_savepoint;
Cursor positions are not affected by savepoint rollback:
BEGIN;
DECLARE foo CURSOR FOR SELECT 1 UNION SELECT 2;
SAVEPOINT foo;
FETCH 1 FROM foo;
?column?
----------
1
ROLLBACK TO SAVEPOINT foo;
FETCH 1 FROM foo;
?column?
----------
2
COMMIT;
COMPATIBILITY
The SQL standard specifies that the key word SAVEPOINT is mandatory, but PostgreSQL and Oracle allow it to be omitted. SQL allows only
WORK, not TRANSACTION, as a noise word after ROLLBACK. Also, SQL has an optional clause AND [ NO ] CHAIN which is not currently supported
by PostgreSQL. Otherwise, this command conforms to the SQL standard.
SEE ALSO
BEGIN(7), COMMIT(7), RELEASE SAVEPOINT (RELEASE_SAVEPOINT(7)), ROLLBACK(7), SAVEPOINT(7)
PostgreSQL 9.2.7 2014-02-17 ROLLBACK TO SAVEPOINT(7)