Some one knows the FileReport job error 255?

Sixto

The FileReport job finalize with this message 'FAILED: Method dm_FileReport return value was 255.'

Any solution?

ldallas

Minor correction in the command line - remove the extra dashes in between filereport and -docbase_name

./dmbasic -f../install/admin/mthd7.ebs -eFileReport -docbase_name cyt_ao_pre.cyt_ao_pre_activo2 -user_name s000232 -password xxxxxx -job_id 080007d280061b29 -method_trace_level 9

ought to launch -

other questions - since it is launching - is it timing out?  how long does it run before it dies, what is the timeout value on the method or is it set to launch async. If the method is set to the default 30 sec then it will never finish - 255 could be the result because the process is killed when the method timesout

see support note

Abstract: Symptoms DM_FileReport job starts but hangs, and finally fails with a "time out" error. Large docbase with more than 54 dm_locations. Change Upgrade from Content Server 525 SP5 to a CS 53

URL:

http://solutions.emc.com/emcsolutionview.asp?id=esg99938

the query to collect object to process could be returning an exceptionally large result set or running poorly because of other conditions. Try the batchhint suggestion in the note.

mszurap

Hi,

Please turn on the Trace Launch option for the dm_fileReport method (use Documentum Administrator for this). After that invoke the job, and see the docbase (content server) log.

What does it say?

Sixto

Hi,

This is the result of the execution of the job.

Wed Jan 28 07:43:40 2009 279549: 1130628[1130628] TRACE LAUNCH: ./dmbasic -f../install/admin/mthd7.ebs -eFileReport  -- -docbase_name cyt_ao_pre.cyt_ao_pre_activo2 -user_name s000232 -job_id 080007d280061b29 -method_trace_level 9
dmExec::ForkLaunch() system(./dmbasic -f../install/admin/mthd7.ebs -eFileReport  -- -docbase_name cyt_ao_pre.cyt_ao_pre_activo2 -user_name s000232 -job_id 080007d280061b29 -method_trace_level 9 )
dmExec::ForkLaunch() returns: 721035, errno: 9
dmExec::ForkLaunch() returning value: -1
dmUnderTaker: waitpid() results:
  Pid:           553066
  Errno:         0
  DeathByExit:   1
  ExitVal:       255
  DeathByStop:   0
  StopVal:       -1
  DeathBySignal: 0
  SigVal:        -1

mszurap

Look at  $DOCUMENTUM/dba/log/<folder_starting_with_zero>/sysadmin/FileReportDoc.txt file. It should exist as the ebs script was executed but returned an error code.

Sixto

Hi,

When the job is executed leaves no error in the report.

Attach file with result of the execution of the job

Thanks in advance

mszurap

Strange. Check the -window_interval value at the job's method tab, maybe it's too low and the content server process kills it if it's running for too long. Try to increase it. Otherwise, log a support request...

ldallas

If memory serves 255 in this instance is a catch all for a failed launch on Unix. Its not leaving a log file because its not actually able to execute

A few things to help diagnose the problem.

check agent_exec.log for additional errors as this is probably where the stderr for this process is going instead of the docbase log

it may provide more detail if you log on to the server as dmadmin - go to the $DOCUMENTUM/bin directory and run the method verb manually -

./dmbasic -f../install/admin/mthd7.ebs -eFileReport  -- -docbase_name cyt_ao_pre.cyt_ao_pre_activo2 -user_name s000232 -job_id 080007d280061b29 -

method_trace_level 9

check space then permissions on the log and dmc cache filesystems (df -k). I have seen this error before when a procedure could not write to stdout.

FileReport output can be huge. Make sure the previous execution hasn't filled it up.

If you are running in a multi-server configuration - make sure that this instance of the job is not being launched by more than one instance of the server -

Sixto

Hi Lee,

The agent_exec.log only report this entry

Wed Jan 28 11:08:13 2009 [INFORMATION] [LAUNCHER 962768] Detected while preparing job dm_FileReport_2 for execution: Agent Exec connected to server cyt_ao_pre_activo2:  [DM_SESSION_I_SESSION_START]info:  "Session 010007d28003c428 started for user s000232."

I run the method verb manually.

./dmbasic -f../install/admin/mthd7.ebs -eFileReport  -- -docbase_name cyt_ao_pre.cyt_ao_pre_activo2 -user_name s000232 -password xxxxxx -job_id 080007d280061b29 -method_trace_level 9

And the result is:

dmbasic: The entry point FileReport  does not exist.

They are not problem with space and permissions and i'm sure that this instance of the job is launched only by one instance of the server.

To try to locate the error I have performed several tests leaving from a folder with little content. The File Report functioned without problems generating a report complete, but when the  number of files in the path surpassed 131 generated the error 255.

In other tests with another different folder the error is generated since 171 files

ldallas

Minor correction in the command line - remove the extra dashes in between filereport and -docbase_name

./dmbasic -f../install/admin/mthd7.ebs -eFileReport -docbase_name cyt_ao_pre.cyt_ao_pre_activo2 -user_name s000232 -password xxxxxx -job_id 080007d280061b29 -method_trace_level 9

ought to launch -

other questions - since it is launching - is it timing out?  how long does it run before it dies, what is the timeout value on the method or is it set to launch async. If the method is set to the default 30 sec then it will never finish - 255 could be the result because the process is killed when the method timesout

see support note

Abstract: Symptoms DM_FileReport job starts but hangs, and finally fails with a "time out" error. Large docbase with more than 54 dm_locations. Change Upgrade from Content Server 525 SP5 to a CS 53

URL:

http://solutions.emc.com/emcsolutionview.asp?id=esg99938

the query to collect object to process could be returning an exceptionally large result set or running poorly because of other conditions. Try the batchhint suggestion in the note.

Sixto

Hi Lee,

I have modified the script of ejecucion of the job as indicates the technical note that you included me and there is funiconado correctly.

The job this functioning without problems.

Thank you so much for your aid.