Re: EMERGENCY! HELP!

A copy of this was sent to "Neil C" <btsscrth_at_bt.com> (if that email address didn't require changing) On Mon, 20 Sep 1999 15:44:34 +0100, you wrote:

>On some platforms you have to include the file format in the
>LOG_ARCHIVE_DEST instead of the the LOG_ARCHIVE_FORMAT, so the entries that
>Brian has are not necessarily wrong.
>

which platforms? I have not heard of that myself.

>NeilC
>
>Frederic DEBRUS wrote in message <01bf0376$5af393c0$3e35a99e_at_gal159a>...
>>
>># oerr ora 270
>>00270, 00000, "error creating archive log %s"
>>// *Cause: An error was encountered when either creating or opening the
>>destination file for archiving.
>>// *Action: Check that the archive destination is valid and that there is
>>sufficient space on the destination device.
>>
>>Did you check permission's on your directory does Oracle user have access
>>to read/write on /users/oracle/logs
>>
>>also
>>
>>define the log as following
>>LOG_ARCHIVE_DEST should only define the destination directory
>>LOG_ARCHIVE_FORMAT there you can define the file name
>>
>>LOG_ARCHIVE_DEST = /users/oracle/logs
>>LOG_ARCHIVE_FORMAT = gte_%S.arc
>>
>>Hope this help
>>
>>
>>
>>Brian Howard <bh_at_creditwatch-inc.com> wrote in article
>><37E64248.F168BE93_at_creditwatch-inc.com>...
>>> I have a critical problem. I currently have twelve people sitting unable
>>> to work. Here is what happened. I had to totally duplicate a server and
>>> database from one server to another to split the database into two
>>> pieces. I bought a new server, installed A/UX on it, installed Oracle
>>> 7.0 on it and after many nights got it up and semi working. I copied
>>> relevant files over to the new server and made a full export on the old
>>> server's database. As I read in the manual, what I believe I needed to
>>> do is get the instance up and running, create all tablespaces and users
>>> and then import the full export. Everything was done: I got the instance
>>> to work and I created all tablespaces and users successfully; however, I
>>> noticed that the archive log destination in the initgte.ora was not
>>> being saved to a directory with adequate space. I changed the directory
>>> to a better location in the initgte.ora file but now when I try to log
>>> in as internal and issue the startup command to bring up the database, I
>>> get the following message:
>>>
>>> SQLDBA> startup
>>> reached here /users/oracle/logs/gte_
>>> ORA-00256: error occurred in translating archive text string
>>> '/users/oracle/logs/gte_'
>>> ORA-00270: error creating archive log
>>> Macintosh A/UX Error: 13: Permission denied
>>>
>>> It was working before I made this change in the log_archive_dest in the
>>> initgte.ora file.
>>>
>>> This is the way those lines look now:
>>> LOG_ARCHIVE_DEST = /users/oracle/logs/gte_
>>> LOG_ARCHIVE_FORMAT = %S.arc
>>>
>>> Please help. This is critical. Thanks.
>>>
>>>
>>>
>

--
See http://govt.us.oracle.com/~tkyte/ for my columns 'Digging-in to Oracle8i'... Current article is "Part I of V, Autonomous Transactions" updated June 21'st  

Thomas Kyte                   tkyte_at_us.oracle.com
Oracle Service Industries     Reston, VA   USA

Opinions are mine and do not necessarily reflect those of Oracle Corporation Received on Mon Sep 20 1999 - 10:13:44 CDT