You can easily "force" the exp utility to include the timestamp of the beginning of the export in the log file. Oracle's exp and imp (and some other utilities) have a very peculiar and unfortunate habit of redirecting some parts of the output to stderr pipe and not to standard output as you would expect. And the header of the exp log output (where the current timestamp is displayed) is one of those parts. If you specify LOG=log.txt when running exp, then only standard output is redirected into the log file. And you won't find any timestamp in there. Here is an example of such a log file that was created with the following exp command line:
c:\exp scott/tiger@o901 file=emp.dmp tables=emp log=log.txt
But if instead of this you redirect the standard error pipe to the log file you get the complete output (as you get on the screen when running exp manualy), together with the timestamp information in the first line (this stderr redirection example is valid for Windows, but it is practicaly the same on Unix):Code:Connected to: Oracle9i Enterprise Edition Release 9.0.1.1.1 - Production With the Partitioning option JServer Release 9.0.1.1.1 - Production Export done in EE8MSWIN1250 character set and AL16UTF16 NCHAR character set About to export specified tables via Conventional Path ... . . exporting table EMP 14 rows exported Export terminated successfully without warnings.
C:\>exp scott/tiger@o901 file=emp.dmp tables=emp 2>log.txt
Code:Export: Release 9.0.1.1.1 - Production on Po Mar 22 19:45:32 2004 (c) Copyright 2001 Oracle Corporation. All rights reserved. Connected to: Oracle9i Enterprise Edition Release 9.0.1.1.1 - Production With the Partitioning option JServer Release 9.0.1.1.1 - Production Export done in EE8MSWIN1250 character set and AL16UTF16 NCHAR character set About to export specified tables via Conventional Path ... . . exporting table EMP 14 rows exported Export terminated successfully without warnings.
Reply With Quote