Re: Full Ex/Im-port to New Instance, NT

Yassir,

  Jurij has explained to you, and I also reiterate that OS authenticated users are no different than proper oracle password authenticated users. Only thing is you don't have to specify the password when you login as OS authenticated user as Oracle uses OS login as authentication method.

 All users ( Os authenticated ones or Password authenticated ) have their objects stored in the tablespaces ( and hence datafiles ) and are exported when you do a full export and later when you do a full import then full import can create them back for you if used properly.

  Don't give any irrelevant reason and please try it out, and then let us know, what problem did you face and what did not come in the imported database as a result of full import.

  I know you are making it it a presitge issue, don't think that I or Jurij want to put you down, we all are learning and not everyone knows everything, the aim of this newsgroup is to get imformed, learn things you don't know or you are confused/mis-informed, correct if you believe or know is wrong, and you have a different opinion.

 I can only say you have to try yourself then only you will know, if you find otherwise then please tell so that I can also learn that.

 take it as a healthy discussion..

 Jurij, thanks for your inputs on this discussions, if I were alone I would have left this topic alone sometime ago.

 We can discuss things and don't force anyone if they have certain beleifs already deeply set in their mind. Hope this clears the issue.

 Yassir, let us know what other doubts you have, again please try it and then make more comments.

 I am liking the discussion and would like to continue if you are interested.

thanks,

Manoj Jain
Oracle Certified Professional - OCP DBA Chauncey Certified Oracle7 DBA

In article <6vlo5h$54k$1_at_newsreader2.core.theplanet.net>,   "Yassir Khogaly" <yassir_at_khogaly.freeserve.co.uk> wrote:
> Hi,
>
> Obviously none of you had any database with OS auth Users having locally
> stored objects,,,
> mjain_at_my-dejanews.com wrote in message <6vlb31$kbt$1_at_nnrp1.dejanews.com>...
> >
> >
> >Yassir,
> >
> > Have you tried what I said in my mail. Try it now.
> >Then let us see what problems you encounter.
> >
> > Jurji also tried to explain you about it in his posting
> >again second time. You can also change the DB_BLOCK_SIZE to
> >a different value than original when you create new database
> >
> >I suggest you try a full export and then do a full import as
> >I and Jurji tried to explain, and if you find any problems then
> >let us look into it, and see what is missing, or what is done
> >wrong.
> >
> > This is only logical way to convince you, I am sure you will be
> >convinced if you try it yourself.
> >
> >good luck,
> >
> >Manoj Jain
> >Oracle Certified Profrssional - OCP DBA
> >Chauncey Certified Oracle7 DBA
> >
> >In article <6vkj9i$dl7$1_at_newsreader1.core.theplanet.net>,
> > "Yassir Khogaly" <yassir_at_khogaly.freeserve.co.uk> wrote:
> >> I will tell you an existing Open TAR with ORACLE UK
> >> Its a Bug On NT4.0 and Corrupt Rollback Segment Header when the
> following
> >> scenario occurs :
> >> 1-If you enable the UNLIMITED MAX EXTENTS while DB_BLOCK_SIZE=2K(DEFAULT)
> >> 2-ENABLE THE DYNAMIC SPACE MANAGEMENT ON DATAFILES LEVEL.
> >> 3-CREATE ANY PRIVATE ROLLBACK SEGMENTS "2 will be perfect".
> >> 4-Start some Procedure, Program, Application ...that accesses the
> Database
> >> and requires to acquire the private rollback segments"AS OWNER".
> >> 5-Now Crash your database by Switching OFF POWER.
> >> 6-Restart the Machine & NT. Your Database will Start.
> >> 7- Check your alert file you will find that Smon tries to Recover some
> >> Transactions..Then Ora600.. .
> >> 8-Your Private Rollback Segments Will become "Needs Recovery", But Will
> >> never ever recover Again".
> >>
> >> 9-ORACLE Corporation Support PROVIDES TWO SOLUTIONS, The First is Using
> >> "_corrupt_rollback_segments" which is Not Recommended because it leaves
> >> Corruption in the Dictionary and the Control File(s). The RECOMMENDED
> >> Solution IS TO RECREATE YOUR DATABASE....!
> >>
> >> 10-DO FULL EXPORT,RE-CREATE THE DATABASE & THE TABLESPACES WITH EXACT
> NAMES
> >> OF DATAFILES and LOCATIONS.
> >> 11-RE-CREATE YOUR PRIVATE ROLLBACK SEGMENTS WITH THE EXACT NAMES, to do
> that
> >> you need to Recreate your Application User then Create the Private
> Rollback
> >> Segments.
> >> 12-IMPORT FULL WITH "IGNORE=y".
> >>
> >> 13-After the Import is Done connect to your database and Drop the Private
> >> Rollback Segments if you want ..But only at this stage your database will
> be
> >> corruption Free...
> >>
> >> Regards
> >>
> >> about
> >> Yassir Khogaly wrote in message
> >> <6vkai7$bkl$1_at_newsreader2.core.theplanet.net>...
> >> >Hi,
> >> >
> >> >Yes.. I Said that and it is correct.
> >> >Read the original emai you will find that the question was about Full
> >> import
> >> >into an new Instance...! Talking about new instances..., Please try out
> >> this
> >> >yourself :
> >> >
> >> >1)-FULLY EXPORT YOUR CURRENT DATABASE.
> >> >2)-DROP YOUR DATABASE COMPLETELY & REMOVE THE DATAFILES physically and
> also
> >> >remove Oracleservice & OracleStart services
> >> >3)-RECREATE YOUR DATABASE WITH ALL EXACT PARAMETERS, Tablespaces,
> Datafiles
> >> >Names & locations, BUT CHANGED DB_BLOCK_SIZE TO 8K from 2K which is the
> >> >default for NT4.0.
> >> >4)-TRY TO IMPORT YOUR PREVIOUS EXPORT now...?.
> >> >
> >> >Please Let me know if you still NOT happy...!
> >> >
> >> >
> >> >Good Luck

-----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own Received on Fri Oct 09 1998 - 22:41:13 CDT