Error: Filename could not be created. Output file is scratch directory. - when running Query and Output

Query and Output may end without creating the output file and the job may have the following error on the output:
 
Filename {filename} could not be created.  Output file is {$HOME/scratch}

In the above, {filename} represents the full output path, and {$HOME/scratch} represents the scratch directory on the database.

For example: 

Filename /export/home/app/ta/[database]/output/users/[username]/1211_purl_alt_id_test could not be created. Output file is /export/home/app/ta/[database]/scratch/
 

 


 
The root cause is the output path is invalid or going someplace that does not exist.

To resolve, you can either
  • Confirm the folder path (in any FTP utility) and rerun the output to that folder
  • Create the missing folder and rerun the output. If you are unable to create the folder, contact Team Approach Support.
-----------------------------------------------------------------------------
Note:  the Output path should contain only lower-case characters.  The filename can be entered with upper-case characters, but as noted below, it will be converted to lower-case.

This output filename will cause an error, because the folder contains upper-case characters:

/export/home/app/ta/devb/output/pbds/test/caSEsenSitive/tesT_outPut.txt

Here is an example of the error in a Queue log:
 
Filename /export/home/app/ta/devb/output/pbds/test/casesensitive/test_output20171106114249.txt could not be created.  Output file is /export/home/app/ta/devb/scratch/pbds

If the Output filename is entered as:

/export/home/app/ta/devb/output/pbds/test/casesensitive/tesT_outPut.txt

The resulting file will be:

/export/home/app/ta/devb/output/pbds/test/casesensitive/test_output.txt

where the folder will be accepted as is, but the output filename (as listed in Query and Output Schedule, in the File Output Options) will have all upper-case characters converted to lowercase.

Environment

 Team Approach
 RSR
 TA

Was this article helpful?


Thanks for your feedback! Did this solve your issue?

Comments (optional):


Thanks for your feedback!
We're glad it was helpful but sorry it didn’t solve your issue. If you need assistance, click Chat with Support below.
We’re sorry to hear that. Please tell us why.

 I don't like how this works.

 The answer is confusing.

 The answer didn't match what I was searching for.

Additional Comments (optional):


Thanks for your feedback! If you need assistance, click Chat with Support below.
Thanks for your feedback. Help us make our products even better by sharing details in our Idea Banks or our online Community.
Thanks for letting us know. We'll work on clarifying the information in the article. If you need assistance, click Chat with Support below.
Thanks for letting us know. We'll work on updating the search engine to return more relevant results.