Prev: how to know the internal representation of a column of clob type
Next: To use Oracle 10g R2 on Linux which distribution?
From: andreik on 16 Mar 2010 11:33 Hi all, I'm trying to investigate a table drop using LogMiner. I can locate the needed SCN and can see the 'DROP' command in V $LOGMNR_CONTENTS along with some internal stuff in one transaction. But for some reason SESSION_INFO is missing for that transacation! Next transaction already comes with session_info. Also when I do a test drop now on the same database, I can nicely see myself in the SESSION_INFO. But for that old transaction SESSION_INFO is not displayed. Anyone has an idea how can I have SESSION_INFO retrieved for that transaction? 10.2.0.1 on Solaris 64bit thanks
From: ddf on 16 Mar 2010 12:01 On Mar 16, 11:33 am, andreik <spamme.andr...(a)gmail.com> wrote: > Hi all, > > I'm trying to investigate a table drop using LogMiner. > > I can locate the needed SCN and can see the 'DROP' command in V > $LOGMNR_CONTENTS along with some internal stuff in one transaction. > But for some reason SESSION_INFO is missing for that transacation! > Next transaction already comes with session_info. Also when I do a > test drop now on the same database, I can nicely see myself in the > SESSION_INFO. But for that old transaction SESSION_INFO is not > displayed. > > Anyone has an idea how can I have SESSION_INFO retrieved for that > transaction? > > 10.2.0.1 on Solaris 64bit > > thanks SESSION_INFO isn't available for that transaction else you'd see it displayed. David Fitzjarrell
From: andreik on 16 Mar 2010 12:10 On Mar 16, 5:01 pm, ddf <orat...(a)msn.com> wrote: > On Mar 16, 11:33 am, andreik <spamme.andr...(a)gmail.com> wrote: > > > > > Hi all, > > > I'm trying to investigate a table drop using LogMiner. > > > I can locate the needed SCN and can see the 'DROP' command in V > > $LOGMNR_CONTENTS along with some internal stuff in one transaction. > > But for some reason SESSION_INFO is missing for that transacation! > > Next transaction already comes with session_info. Also when I do a > > test drop now on the same database, I can nicely see myself in the > > SESSION_INFO. But for that old transaction SESSION_INFO is not > > displayed. > > > Anyone has an idea how can I have SESSION_INFO retrieved for that > > transaction? > > > 10.2.0.1 on Solaris 64bit > > > thanks > > SESSION_INFO isn't available for that transaction else you'd see it > displayed. > > David Fitzjarrell so this is normal that session_info does not always get logged into redo? what does it depend on? is this mentioned somewhere in the documentation? I couldn't find anything like that.
From: ddf on 16 Mar 2010 13:00 On Mar 16, 12:10 pm, andreik <spamme.andr...(a)gmail.com> wrote: > On Mar 16, 5:01 pm, ddf <orat...(a)msn.com> wrote: > > > > > > > On Mar 16, 11:33 am, andreik <spamme.andr...(a)gmail.com> wrote: > > > > Hi all, > > > > I'm trying to investigate a table drop using LogMiner. > > > > I can locate the needed SCN and can see the 'DROP' command in V > > > $LOGMNR_CONTENTS along with some internal stuff in one transaction. > > > But for some reason SESSION_INFO is missing for that transacation! > > > Next transaction already comes with session_info. Also when I do a > > > test drop now on the same database, I can nicely see myself in the > > > SESSION_INFO. But for that old transaction SESSION_INFO is not > > > displayed. > > > > Anyone has an idea how can I have SESSION_INFO retrieved for that > > > transaction? > > > > 10.2.0.1 on Solaris 64bit > > > > thanks > > > SESSION_INFO isn't available for that transaction else you'd see it > > displayed. > > > David Fitzjarrell > > so this is normal that session_info does not always get logged into > redo? > what does it depend on? > is this mentioned somewhere in the documentation? I couldn't find > anything like that.- Hide quoted text - > > - Show quoted text - Apparently supplemtal logging wasn't enabled at the time the suspect transaction took place as this is required to populate session_info data in the redo logs. David Fitzjarrell
From: ddf on 16 Mar 2010 13:17
On Mar 16, 12:10 pm, andreik <spamme.andr...(a)gmail.com> wrote: > On Mar 16, 5:01 pm, ddf <orat...(a)msn.com> wrote: > > > > > > > On Mar 16, 11:33 am, andreik <spamme.andr...(a)gmail.com> wrote: > > > > Hi all, > > > > I'm trying to investigate a table drop using LogMiner. > > > > I can locate the needed SCN and can see the 'DROP' command in V > > > $LOGMNR_CONTENTS along with some internal stuff in one transaction. > > > But for some reason SESSION_INFO is missing for that transacation! > > > Next transaction already comes with session_info. Also when I do a > > > test drop now on the same database, I can nicely see myself in the > > > SESSION_INFO. But for that old transaction SESSION_INFO is not > > > displayed. > > > > Anyone has an idea how can I have SESSION_INFO retrieved for that > > > transaction? > > > > 10.2.0.1 on Solaris 64bit > > > > thanks > > > SESSION_INFO isn't available for that transaction else you'd see it > > displayed. > > > David Fitzjarrell > > so this is normal that session_info does not always get logged into > redo? > what does it depend on? > is this mentioned somewhere in the documentation? I couldn't find > anything like that.- Hide quoted text - > > - Show quoted text - Presumsing you have a valid support contract you should read Metalink document 110301.1. Since you're running an unpatched 10.2.0.1 installation you may not be in possession of a valid CSI so reading that document may not be possible. David Fitzjarrell |