Error in creating log files in create script with ASM

In our create script we have:
LOGFILE GROUP 1 ('+REDO1/oradata/cssys/redo01a.log') SIZE 100M;
I'm getting the error ORA-00301: error adding log file '+REDO1/oradata/cssys/redo01a.log' - file cannot be created.
ORA-17502: ksfdcre:4 Failed to create file +REDO1/oradata/cssys/redo01a.log
ORA-15173: entry 'oradata' does not exist in directory '/'
The datafile didn't return an error and there we had DATAFILE '+DATA/oradata/cssys/system01.dbf.........
Not sure why the error occurs on the REDO, the DATA and REDO look fine in ASM. Thanks in advance.

I have no personal experience with this, but pl see if MOS Doc 604982.1 (Unable To duplicate Database on ASM From one Server To Another Host) is applicable in your case
HTH
Srini

Similar Messages

Create log File for my Script

i need two things for my powershell script
1-show successful message if script run successfully
2- if script run with error write error in log file
Please Guide me
$Folders1 = "C:\inetpub\temp\YYY"
cd $Folders1
md $Folders1\Change
Copy-Item * Change -recurse -Force -Exclude Change
md $Folders1\Change\IPC
Move-Item Change\ZZZ Change\ZZZ
xcopy ZZZ Change\IPC\ZZZ /s /i
xcopy OrgFundamental Change\IPC\OrgFundamental /s /i
xcopy Card Change\Card-ib /s /i
$Folders2 = Get-ChildItem $Folders1\Change
foreach($f in $Folders2)
if ($f.name -notlike "IPC" -and $f.name -notlike "CardScheduler" -and $f.name -notlike "Scheduler")
md Change\$f\bin
Move-Item Change\$f\*.dll Change\$f\bin
Get-ChildItem -Path Change\$f "*.exe.config" | Rename-Item -NewName web.config

This is sort of separate from error handling, but when it comes to logging what happens in my scripts, I have two approaches. If the system is running PowerShell 3.0 or later, and I don't care about console output (say, if the script is running as a scheduled
task, and no one will be looking at it interactively anyway), then sometimes I'll run the script like this:
PowerShell.exe -NoProfile -File 'c:\path\to\myScript.ps1' *> 'c:\Logs\someLogFile.txt'
The *> operator (introduced in PowerShell 3.0) redirects the Output, Error, Warning, Verbose and Debug streams, in this case, redirecting them all to a file.
More frequently, though, I use the
PowerShellLogging module. This has a few advantages over the redirection operator:
It works with PowerShell 2.0.
Output can be displayed both on-screen and sent to a log file, with minimal modification to the script code.
You can easily control which streams go to which files in any combination you like.
You can control the content of what gets sent to the log file. When using the stock Enable-LogFile cmdlet, you automatically get date and timestamps prepended to each non-blank line in the file.
Using this module in a script only requires two lines of code (and possibly only one, if you're running PowerShell 3.0 or later with module auto-loading enabled):
Import-Module PowerShellLogging
$logFile = Enable-LogFile -Path 'c:\Logs\someLogFile.txt'
It's also a good idea (but not strictly required) to pass your $logFile object to Disable-LogFile when your script finishes, so no other console output bleeds into your log file before the garbage collector comes along and stops that from happening.

Create database fails with error ORA-01505: error in adding log files

hi all,
hope someone can help me out, I'm trying to create a database using a SQL script, the content of the script is:
create database testora
user sys identified by oracle
user system identified by oracle
logfile group 1 ('/u01/app/oracle/oradata/testora/redo01a.log', '/u02/app/oracle/oradata/testora/redo01b.log') size 100m blocksize 512 reuse,
     group 2 ('/u01/app/oracle/oradata/testora/redo02a.log', '/u02/app/oracle/oradata/testora/redo02b.log') size 100m blocksize 512 reuse,
     group 3 ('/u01/app/oracle/oradata/testora/redo03a.log', '/u02/app/oracle/oradata/testora/redo03b.log') size 100m blocksize 512 reuse,
maxlogfiles 5
maxlogmembers 5
maxdatafiles 100
character set US7ASCII
national character set AL16UTF16
extent management local
datafile '/u01/app/oracle/oradata/testora/system01.dbf' size 400m reuse
sysaux datafile '/u01/app/oracle/oradata/testora/sysaux01.dbf' size 400m reuse
default tablespace users
     datafile '/u02/app/oracle/oradata/testora/users01.dbf' size 500m reuse autoextend on maxsize unlimited
default temporary tablespace tempts1
     tempfile '/u01/app/oracle/oradata/testora/temp01.dbf' size 20m reuse autoextend on maxsize 4g
undo tablespace undotbs1
     datafile '/u01/app/oracle/oradata/testora/undotbs01.dbf' size 200m reuse autoextend on maxsize unlimited
It fails in creating the database with the following output:
SQL> @/home/oracle/Oracle_Scripts/testora_db_script.sql
create database testora
ERROR at line 1:
ORA-01092: ORACLE instance terminated. Disconnection forced
ORA-01501: CREATE DATABASE failed
ORA-01505: error in adding log files
ORA-01184: logfile group 1 already exists
Process ID: 3486
Session ID: 1 Serial number: 3

sorry to revive this thread but i have one more issue with this. I created a database with DBCA insetead of CREATE DATABASE command and selected option for Fast Recovery Area space. This automatically set initialization parameter db_recovery_file_dest and db_recovery_file_dest_size, but did not create a OMF redo log group, but instead created three redo log groups with 1 member each.
select * from v$logfile returns:
1          ONLINE     /u01/app/oracle/oradata/testdb2/redo01.log     NO
2          ONLINE     /u01/app/oracle/oradata/testdb2/redo02.log     NO
3          ONLINE     /u01/app/oracle/oradata/testdb2/redo03.log     NO
Any idea why if creating a database with create database command and specifying db_recovery_file_dest creates an OMF redo log group and with DBCA it doesn't?

Problem in creating log file on Ubuntu(Linux)

hi
I have developed a project in java. which creates log file for exception handling. This is working fine on Windows but When I run the jar file on ubuntu then it is not creating log file and throwing an error.
Error Message="Permission Denied UnixFileSystem.java createFileExclusively()"
Code is :
strStartupPath = new java.io.File("").getAbsolutePath();
DateFormat dateformat = new SimpleDateFormat("yyyyMMdd");
Date date = new Date();
String strFileName = strStartupPath + "\\" + dateformat.format(date) + ".log";
File logFile = new File(strFileName);
Your assistance will be appriciated.
Sonal

If you want to do this properly then you will have to make it OS specific. Various security systems on each platform will prevent you from freely writing your logfile unless you choose the correct location. The applications folder under MacOSX, for instance, requires Admin privileges. Under MacOSX and Windows, log files are typically stored in the Applications Data resp. /Library/Logs or ~/Library/Logs folder in MacOS X. In Unix and Linux you will typically use /var/log directory.
I think your question is rather Java than Linux specific, but there is a lot of information available for free on the web.
Perhaps the following example can help you to determine the OS:
public static final class OsUtils
   private static String OS = null;
   public static String getOsName()
      if(OS == null) { OS = System.getProperty("os.name");
   public static boolean isWindows()
      return getOsName().startsWith("Windows");
   public static boolean isUnix() // and so on
}Edited by: Dude on Apr 16, 2011 12:58 AM

Age of Mythology cannot create log file

I am trying to set up the game "Age of Mythology" on my son's user account. I am the administrator, and it works fine in my account, but when I try to run it from his account, I get the "cannot create log file" error message.
I've tried doing an install under his user name, but still get this message.
An thoughts?
Thanks,
Boris

This sounds like a permissions issue. You probably need to enable read and write access to the folder where the log file is created. From your administrator account, Get info on that folder > expand Ownership and Permissions > expand Details > change Others to Read and Write.
PowerMac G5 Mac OS X (10.4.6) 1GB RAM, nvidia 6800 ultra, Apple 30" Cinema Display

Log file not creating

Hi, I tried to configure log for my application, but the log files are not getting created, I am getting the following error.
My log configuration -
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE log-configuration SYSTEM "log-configuration.dtd">
<log-configuration>
     <log-destinations>
          <log-destination
               count="10"
               effective-severity="ALL"
               limit="10000"
               name="LogTestLog"
               pattern="./log/applications/TestLog/LogTestLog.%g.log"
               type="FileLog"/>
     </log-destinations>
     <log-controllers>
          <log-controller
               effective-severity="ALL"
               name="System.out">
               <associated-destinations>
                    <destination-ref
                         association-type="LOG"
                         name="LogTestLog"/>
               </associated-destinations>
          </log-controller>
          <log-controller
               effective-severity="ALL"
               name="com.giri.test.LogServlet">
               <associated-destinations>
                    <destination-ref
                         association-type="LOG"
                         name="LogTestLog"/>
                    <anonymous-destination
                         association-type="LOG"
                         type="FileLog"/>
               </associated-destinations>
          </log-controller>
     </log-controllers>
</log-configuration>
#1.5#0030485D5AE617CD000000000000142000042AAA6682264C#1172811259302#/System/Logging##com.sap.tc.logging.FileLogInfoData.[getFileHeader(String fileName, int cntHeadLines)]######147f6460c87a11dba2920030485d5ae6#SAPEngine_System_Thread[impl:5]_99##0#0#Warning##Java#SAP_LOGGING_UNEXPECTED##Unexcepted error occured on !#1#FileHeader parsing#
#1.5#0030485D5AE617CD000000010000142000042AAA6682297F#1172811259302#/System/Logging##/System/Logging######147f6460c87a11dba2920030485d5ae6#SAPEngine_System_Thread[impl:5]_99##0#0#Path##Java###Caught #1#java.lang.Exception: .
log
applications
TestLog
LogTestLog.0.log (The system cannot find the path specified)
     at com.sap.tc.logging.FileLogInfoData.getEOLLength(FileLogInfoData.java:432)
     at com.sap.tc.logging.FileLogInfoData.getFileHeaderLines(FileLogInfoData.java:348)
     at com.sap.tc.logging.FileLogInfoData.getFileHeaderLines(FileLogInfoData.java:334)
     at com.sap.tc.logging.FileLogInfoData.loadFileLogHeader(FileLogInfoData.java:320)
     at com.sap.tc.logging.FileLogInfoData.init(FileLogInfoData.java:260)
     at com.sap.tc.logging.FileLogInfoData.<init>(FileLogInfoData.java:119)
     at com.sap.tc.logging.FileLog.init(FileLog.java:373)
     at com.sap.tc.logging.FileLog.<init>(FileLog.java:282)
     at com.sap.tc.logging.FileLog.<init>(FileLog.java:246)
     at com.sap.engine.services.log_configurator.admin.LogConfigurator.adjustConfiguration(LogConfigurator.java:665)
     at com.sap.engine.services.log_configurator.admin.LogConfigurator.applyConfiguration(LogConfigurator.java:1488)
     at com.sap.engine.services.log_configurator.LogConfiguratorContainer.prepareStart(LogConfiguratorContainer.java:545)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:239)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:187)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:327)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runMe(ParallelAdapter.java:74)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter$1.run(ParallelAdapter.java:218)
     at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
     at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
     at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)

I have the same problem. I also see many similar exception from different apps, such as writing to file ".
log
applications
cms
default.0.trc", ".
log
applications
cms
default.0.trc"
Do I have to create log file before I use the logging service.
I change "ForceSingleTraceFile" to "NO" in "LogManager" by Visual Administrator. Could it be a problem?
I am running SAP Web AS 6.4 and deploying using SDM. I have a log-configuration.xml in the ear file. This is my log configuration
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE log-configuration SYSTEM "log-configuration.dtd">
<log-configuration>
     <log-formatters/>
     <log-destinations>
          <log-destination
               count="10"
               effective-severity="ALL"
               limit="1000000"
               name="TraceLog01"
               pattern="./log/file.%g.trc"
               type="FileLog"/>
     </log-destinations>
     <log-controllers>
          <log-controller
               effective-severity="ALL"
               name="LogController01">
               <associated-destinations>
                    <destination-ref
                         association-type="LOG"
                         name="TraceLog01"/>
               </associated-destinations>
          </log-controller>
     </log-controllers>
</log-configuration>

Why multiple log files are created while using transaction in berkeley db

we are using berkeleydb java edition db base api, we have already read/write CDRFile of 9 lack rows with transaction and
without transaction implementing secondary database concept the issues we are getting are as follows:-
with transaction----------size of database environment 1.63gb which is due to no. of log files created each of 10 mb.
without transaction-------size of database environment 588mb and here only one log file is created which is of 10mb. so we want to know how REASON CONCRETE CONCLUSION ..
how log files are created and what is meant of using transaction and not using transaction in db environment and what are this db files db.001,db.002,_db.003,_db.004,__db.005 and log files like log.0000000001.....plz reply soon

we are using berkeleydb java edition db base api, If you are seeing __db.NNN files in your environment root directory, these are environment's shared region files. And since you see these you are using Berkeley DB Core (with the Java/JNI Base API), not Berkeley DB Java Edition.
with transaction ...
without transaction ...First of all, do you need transactions or not? Review the documentation section called "Why transactions?" in the Berkeley DB Programmer's Reference Guide.
without transaction-------size of database environment 588mb and here only one log file is created which is of 10mb.There should be no logs created when transactions are not used. That single log file has likely remained there from the previous transactional run.
how log files are created and what is meant of using transaction and not using transaction in db environment and what are this db files db.001,db.002,_db.003,_db.004,__db.005 and log files like log.0000000001Have you reviewed the basic documentations references for Berkeley DB Core?
- Berkeley DB Programmer's Reference Guide
in particular sections: The Berkeley DB products, Shared memory regions, Chapter 11. Berkeley DB Transactional Data Store Applications, Chapter 17. The Logging Subsystem.
- Getting Started with Berkeley DB (Java API Guide) and Getting Started with Berkeley DB Transaction Processing (Java API Guide).
If so, you would have had the answers to these questions; the __db.NNN files are the environment shared region files needed by the environment's subsystems (transaction, locking, logging, memory pool buffer, mutexes), and the log.MMMMMMMMMM are the log files needed for recoverability and created when running with transactions.
--Andrei

Unable to combine files on acrobat 8 getting error message "no PDF file was created beacuse Acrobat encountered an unidentified error"

unable to combine files on acrobat 8 getting error message "no PDF file was created beacuse Acrobat encountered an unidentified error" Please help

A lot of the time the files can not be combined because of incompatible fonts, or at least font sets that could not be resolved. Maybe that will give you some direction to look at.

SHADOW_IMPORT_UPG1 is very very slow, no log files are created

Hi all
We are now doing our production upgrade, during the SHADOW_IMPORT_UPG1 phase system is very slow
no log files are created in the /usr/sap/put/log directory.
only three files are growing in /usr/sap/tmp directory
orar3p> ls -lrt
total 219176
-rw-rw-rw-   1 r3padm     sapsys        2693 Aug 15 18:42 UCMIG_DE.ECO
-rw-rw-rw-   1 r3padm     sapsys        2374 Aug 15 18:42 R3trans.out
-rw-rw-rw-   1 r3padm     sapsys        2685 Aug 15 18:46 ADDON_TR.ECO
-rw-rw-rw-   1 r3padm     sapsys         726 Aug 15 20:04 crshdusr.log
-rw-rw-rw-   1 r3padm     sapsys        3915 Aug 15 21:53 EU_IMTSK.ECO
-rw-rw-r--   1 r3padm     sapsys         257 Aug 15 22:09 SAPKKLFRN18.R3P
-rw-rw-r--   1 r3padm     sapsys         257 Aug 15 22:09 SAPKKLPTN18.R3P
-rw-rw-r--   1 r3padm     sapsys         257 Aug 15 22:09 SAPKKLESN18.R3P
-rw-rw-r--   1 r3padm     sapsys     36433272 Aug 15 23:44 SAPKLESN18.R3P
-rw-rw-r--   1 r3padm     sapsys     36807577 Aug 15 23:44 SAPKLFRN18.R3P
-rw-rw-r--   1 r3padm     sapsys     35372350 Aug 15 23:44 SAPKLPTN18.R3P
orar3p> date
Fri Aug 15 23:44:54 PDT 2008
Can anyone help what to do
Thanks
Senthil

Hello,
did you discover what the cause was for this phase running so slow? And how long did it take to complete in the end?
We are currently running an upgrade of our Development system and have struck the same issue.
I killed the upgrade after the phase had been running for 4 hours and restarted it, but it looks like it is still going to run for a long time.
Regards....John

LOG FILE for batch scripting in MAXL

Hello,
I just wanted to know how to create a LOG FILE for batch scripting.
essmsh E:\Batch\Apps\TOG_DET\Scripts\unload_App.msh
copy e:\batch\apps\tog_det\loadfile\gldetail.otl e:\hyperion\analyticservices\app\tog_det\gldetail /Y
essmsh E:\Batch\Apps\TOG_DET\Scripts\Build_Hier_Data.msh
REM
ECHO OFF
ECHO Loading GL actuals into WFS \ Combined......
E:\HYPERION\common\Perl\5.8.3\bin\MSWin32-x86-multi-thread\PERL.EXE E:\Batch\Apps\WFS.COMBINED\AMLOAD\WFSUATAMLOAD.PLX
E:\HYPERION\common\Perl\5.8.3\bin\MSWin32-x86-multi-thread\PERL.EXE E:\Batch\Apps\WFS.COMBINED\AMLOAD\WFSUATAMLOAD.PLX
Drop object d:\NDM\Data\StampFiles\STAMPLOADBKUP.csv of type outline force;
Alter object d:\NDM\Data\StampFiles\STAMPLOAD_cwoo.csv of type outline rename to d:\NDM\Data\StampFiles\STAMPLOADBKUP.CSV;
SET LogFile=E:\Batch\Apps\TOG_DET\Logs.log
This file does not generate log file can any help me what might be the problem? Even though some of the steps above are not correct it should generate me log file atleast. I need syntax or whatever it is to generate Log file.
Regards
Soma

I wanted to have a logfile of the following batch script regardless of whether the script is running or not.
essmsh E:\Batch\Apps\TOG_DET\Scripts\unload_App.msh
copy e:\batch\apps\tog_det\loadfile\gldetail.otl e:\hyperion\analyticservices\app\tog_det\gldetail /Y
essmsh E:\Batch\Apps\TOG_DET\Scripts\Build_Hier_Data.msh
REM
ECHO OFF
ECHO Loading GL actuals into WFS \ Combined......
E:\HYPERION\common\Perl\5.8.3\bin\MSWin32-x86-multi-thread\PERL.EXE E:\Batch\Apps\WFS.COMBINED\AMLOAD\WFSUATAMLOAD.PLX
Drop object d:\NDM\Data\StampFiles\STAMPLOADBKUP.csv of type outline force;
Alter object d:\NDM\Data\StampFiles\STAMPLOAD_cwoo.csv of type outline rename to d:\NDM\Data\StampFiles\STAMPLOADBKUP.CSV;
What I really want is I need a log file of the above batch script, how the above scripts are running. I do not care whether they are giving me positive results but I need to know what is happening in logfile. HOw will the log file be generated.
Regards
SOma

Error opening installation log file.

ProblemYou are unable to install BlackBerry Desktop Manager and the following error message is displayed when you open the installation log file:
Error opening installation log file verify that the specified log file exist and is writable.
ResolutionTo resolve this issue, edit the system environment variables by completing the following steps:
Warning: The following procedure requires modifying the computer environment variables. This can result in unexpected system behavior. Document the existing values prior to implementing any changes. To search for the Install.log file or files in the temp folder:
On the Start menu, click Run and type %temp%.
Click OK.
In the Temp folder, click Search and then All files and folders. In the All or part of the file name field, type Install.log and set the Look in field value to Temp.
Click Search.
If the Install.log file is found, delete it.
In Windows® Explorer, go to the C:\ drive and create a new folder called TEMP2.
Open the Control Panel and double-click the System icon.
On the Advanced tab, click Environment Variables.
In the User variables list, select TEMP and click Edit.
In the Variable value field, change the file path to C:\TEMP2 and click OK.
In the User variables list, select TMP and click Edit.
In the Variable value field, change the file path to C:\TEMP2 and click OK.
In the Environment Variables window, click OK.
In the System Properties window, click Apply and then OK.
Restart the computer for the changes to take effect.
Repeat the installation procedure for BlackBerry Desktop Manager.
I have 8330

hello,
another solution is here :
http://supportforums.blackberry.com/rim/board/message?board.id=BlackBerryDesktopSoftware&message.id=...
The search box on top-right of this page is your true friend, and the public Knowledge Base too:

RMAN success, but errors in alert.log file

My RMAN backup script runs well, but generates errors in alert.log file.
Here is the trace file contents:
/usr/lib/oracle/xe/app/oracle/admin/XE/udump/xe_ora_3990.trc
Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production
ORACLE_HOME = /usr/lib/oracle/xe/app/oracle/product/10.2.0/server
System name: Linux
Node name: plockton
Release: 2.6.18-128.2.1.el5
Version: #1 SMP Wed Jul 8 11:54:54 EDT 2009
Machine: i686
Instance name: XE
Redo thread mounted by this instance: 1
Oracle process number: 26
Unix process pid: 3990, image: oracle@plockton (TNS V1-V3)
*** 2009-07-23 23:05:01.835
*** ACTION NAME:(0000025 STARTED111) 2009-07-23 23:05:01.823
*** MODULE NAME:(backup full datafile) 2009-07-23 23:05:01.823
*** SERVICE NAME:(SYS$USERS) 2009-07-23 23:05:01.823
*** SESSION ID:(33.154) 2009-07-23 23:05:01.823
*** 2009-07-23 23:05:18.689
*** ACTION NAME:(0000045 STARTED111) 2009-07-23 23:05:18.689
*** MODULE NAME:(backup archivelog) 2009-07-23 23:05:18.689
Does anyone know why? Thanks.
Richard

I'm not sure if this will answer your question or not, but I believe these messages can likely be ignored.
I'm currently running 10.2.0.1.0 Enterprise Edition in pre-production (yes, I know I should apply the latest patchset and I plan to do so as soon as I get a development box allocated to me and can test it's impact). I see the same types of messages that you've reported with each of my regularly-scheduled backups:
a) The alert_<$SID>.log reports that there are errors in trace files:
Mon Aug 10 04:33:49 2009
Starting control autobackup
Mon Aug 10 04:33:50 2009
Errors in file /opt/oracle/admin/blah/udump/blah_ora_32520.trc:
Mon Aug 10 04:33:50 2009
Errors in file /opt/oracle/admin/blah/udump/blah_ora_32520.trc:
Mon Aug 10 04:33:50 2009
Errors in file /opt/oracle/admin/blah/udump/blah_ora_32520.trc:
Control autobackup written to DISK device
handle '/backup/physical/BLAH/RMAN/cf_c-2740124895-20090810-00'
b) The .trc files, when you look at them contain no errors - only these "informational" messages:
*** 2009-08-10 04:33:50.781
*** ACTION NAME:(0000105 STARTED111) 2009-08-10 04:33:50.754
*** MODULE NAME:(backup archivelog) 2009-08-10 04:33:50.754
*** SERVICE NAME:(SYS$USERS) 2009-08-10 04:33:50.754
*** SESSION ID:(126.28030) 2009-08-10 04:33:50.754
c) I've verified that LOG_ARCHIVE_TRACE is set to 0:
SQL*Plus> show parameter log_archive_trace
NAME TYPE VALUE
log_archive_trace integer 0
As best I can discern from my own experience, these should just be ignored and I trust (read: "hope") they will simply go away once the latest patchset is applied. As for you running Oracle XE, a patchset is not an option, unfortunately.
V/R
-Eric

"Error opening installation log file" when installing Photoshop Elements 10

I bought Photoshop Elements 10 , Premiere Elements 10 .... I got the Premiere to download no problem but i can't get the photoshop to download. This is the msg that I am getting when I try to dl it "Error opening installation log file. Verify that the specified log file location exsists and is writable". Not sure why I can download one and not the other since they are both on the same disc. Plus in the program that I purchased I has 5 DVD's. Any suggestions??
Thanks
Message title was edited by: Brett N

Install Premiere Elements, Photoshop Elements
Mylenium

9.3.1- Not able to see more than 1 errors in application.log file

Hi,
In 9.3.1. version, I am not able to see more than 1 errors in application.log file during dataload without rules files.
If anybody has faced this solution, pls let me know the cause.
Thanks
jazz

Hey Jazz,
in the first row add a rule file with no load file change the path to what you want. then insert a new row add your load file here. it should have the path from the previous row in the error file. Then delete the first row and run. I had to do this for a level zero load and was the only thing I could figure out so far

Errors in Alert log file

Hi,
I have encountered following errors in alrt log file, its strange to see FAST_START_MTTR_TARGET is out of valid and aksing to use another value and that value is changing every second, it should be in increasing order or it should be consistent. I think i have a serious problem, so anyone could help me out on this. I am getting this "FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 24381 instead" error regurarly.
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 24381 instead.
Wed Jan 16 23:40:34 2008
Completed checkpoint up to RBA [0x2aadb.2.10], SCN: 5473742880
Wed Jan 16 23:45:51 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 24017 instead.
Wed Jan 16 23:46:21 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 23647 instead.
Wed Jan 16 23:46:52 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 23298 instead.
Wed Jan 16 23:47:22 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 22906 instead.
Wed Jan 16 23:47:52 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 22507 instead.
Wed Jan 16 23:48:22 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 22133 instead.
Wed Jan 16 23:48:52 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 21786 instead.
Wed Jan 16 23:49:22 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 21443 instead.
Wed Jan 16 23:49:52 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 21062 instead.
Wed Jan 16 23:50:22 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 20698 instead.
Wed Jan 16 23:53:53 2008
Incremental checkpoint up to RBA [0x2aadb.31b4.0], current log tail at RBA [0x2aadb.3e38.0]
Thu Jan 17 00:00:54 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 19582 instead.
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 16287 instead.
Thu Jan 17 00:34:01 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 15902 instead.
Thu Jan 17 00:34:31 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 14638 instead.
Thu Jan 17 00:35:01 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 13600 instead.
Thu Jan 17 00:35:31 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 12773 instead.
Thu Jan 17 00:36:02 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 12460 instead.
Thu Jan 17 00:36:32 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 12338 instead.
Thu Jan 17 00:37:01 2008
Process P187 died, see its trace file
Thu Jan 17 00:37:02 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 12248 instead.
Thu Jan 17 00:37:02 2008
Process P188 died, see its trace file
Thu Jan 17 00:37:03 2008
Process P189 died, see its trace file
Thu Jan 17 00:37:04 2008
Process P190 died, see its trace file
Thu Jan 17 00:37:16 2008
Process J000 died, see its trace file
Thu Jan 17 00:37:16 2008
kkjcre1p: unable to spawn jobq slave process
Thu Jan 17 00:37:16 2008
Errors in file /oracle/BP3/saptrace/background/bp3_cjq0_4788.trc:
Process J000 died, see its trace file
Thu Jan 17 00:37:22 2008
kkjcre1p: unable to spawn jobq slave process
Thu Jan 17 00:37:22 2008
Errors in file /oracle/BP3/saptrace/background/bp3_cjq0_4788.trc:
Thanks
Jafar

This parameter, FAST_START_MTTR_TARGET ranges from 0 to 3600 seconds. It is important to specify your oracle version, since a similar issue is reported for the 10gR1 release.
The solution for it would be to increase the value to the suggested one in the alert.log file, but it could be completely out of range from the valid values, so set it to zero and let the oracle instance calculate the value. You can check the output at the V$INSTANCE_RECOVERY view at the columns TARGET_MTTR, and ESTIMATED_MTTR prior to proceeding with modificaiton.
On the other hand, I suggest you to read this metalink note
Kkjcre1p: Unable To Spawn Jobq Slave Process, Error 1089
Doc ID: Note:344275.1
for the Kkjcre1p error message.
~ Madrid

Error in creating log files in create script with ASM

Similar Messages

Maybe you are looking for