oracle 让sys用户执行exp导出操作

[oracle@localhost ~]$ exp sys/abcdefg as sysdba full=y file=/tmp/full100.dmp

LRM-00108: invalid positional parameter value 'as'

EXP-00019: failed to process parameters, type 'EXP HELP=Y' for help

EXP-00000: Export terminated unsuccessfully

[oracle@localhost ~]$ exp \"sys/abcdefg as sysdba\" full=y file=/tmp/full100.dmp

Export: Release 10.2.0.1.0 - Production on Tue Jul 8 09:27:56 2008

Copyright (c) 1982, 2005, Oracle. All rights reserved.

Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production

With the Partitioning, OLAP and Data Mining options

Export done in US7ASCII character set and AL16UTF16 NCHAR character set

server uses WE8ISO8859P1 character set (possible charset conversion)

About to export the entire database ...

. exporting tablespace definitions

. exporting profiles

. exporting user definitions

. exporting roles

. exporting resource costs

. exporting rollback segment definitions

. exporting database links

. exporting sequence numbers

. exporting directory aliases

. exporting context namespaces

. exporting foreign function library names

. exporting PUBLIC type synonyms

. exporting private type synonyms

. exporting object type definitions

. exporting system procedural objects and actions

. exporting pre-schema procedural objects and actions

. exporting cluster definitions

. about to export SYSTEM's tables via Conventional Path ...

. . exporting table DEF$_AQCALL 0 rows exported

. . exporting table DEF$_AQERROR 0 rows exported

. . exporting table DEF$_CALLDEST 0 rows exported

EXP-00091: Exporting questionable statistics.

EXP-00091: Exporting questionable statistics.

EXP-00091: Exporting questionable statistics.

反斜杠加单引号也行

[oracle@localhost ~]$ exp \'sys/abcdefg as sysdba\' full=y file=/tmp/full100.dmp

Export: Release 10.2.0.1.0 - Production on Tue Jul 8 09:28:54 2008

Copyright (c) 1982, 2005, Oracle. All rights reserved.

Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production

With the Partitioning, OLAP and Data Mining options

Export done in US7ASCII character set and AL16UTF16 NCHAR character set

server uses WE8ISO8859P1 character set (possible charset conversion)

About to export the entire database ...

. exporting tablespace definitions

. exporting profiles

. exporting user definitions

. exporting roles

. exporting resource costs

. exporting rollback segment definitions

. exporting database links

. exporting sequence numbers

. exporting directory aliases

. exporting context namespaces

. exporting foreign function library names

以下是官方文档说明:

1. Command line.

Enclose the connect string with a single quote character:

Windows:

D:\> exp 'sys/change_on_install@instance as sysdba' tables=scott.emp

Unix (you need to 'escape' the single quote):

> exp \'sys/change_on_install@instance as sysdba\' tables=scott.emp

VMS (use [double_quote][single_quote]...[single_quote][double_quote]):

$ exp "'sys/change_on_install@instance as sysdba'" tables=scott.emp

Note that this VMS syntax is also a valid syntax on Unix and on Windows.

2. Interactive

Do not specify any connect string on the command line, so you will be prompted to enter it. E.g.:

> exp tables=scott.emp

Export: Release 10.2.0.3.0 - Production on Fri Jun 25 07:39:46 2004

Copyright (c) 1982, 2005, Oracle. All rights reserved.

Username: sys/change_on_install@instance as sysdba

Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - Production

... etc.

3. Parameter file.

You can also specify the username in the parameter file. In this situation, you have to enclose the connect string with a double quote character. However, to prevent possible security breaches we advice you to stop using the USERID parameter in a parameter file.

File: exp.par

---------------

USERID="sys/change_on_install@instance as sysdba"

TABLES=scott.emp

Run export with:

> exp parfile=exp.par

4. Remarks.

Remark 1. If you have setup operating system authentication, it is not necessary to specify the SYS schema name, and password. E.g.:

> exp "'/@instance as sysdba'" tables=scott.emp

Remark 2. In addition, if you have set the environment variable TWO_TASK (on Unix) or LOCAL (on Windows) or on the server where the database is installed you have set ORACLE_HOME and ORACLE_SID, it is not necessary to specify the @instance. E.g.:

> exp "'/ as sysdba'" tables=scott.emp

Remark 3. The export parameters FLASHBACK_SCN and FLASHBACK_TIME cannot be used if the user that invoked the export is connected AS SYSDBA.