Export:
export NLS_CHARACTERSET=WE8ISO8859P1
export NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1
exp system@karen file=karen.dmp,  full=y, log=karen_exp.log, compress=n, direct=y

Invoking Export As SYSDBA
SYSDBA is used internally and has specialized functions; 
its behavior is not the same as for generalized users.
Therefore, you should not typically need to invoke Export as SYSDBA, 
except in the following situations:
1) At the request of Oracle technical support
2) When using transportable tablespaces

exp \'username/password AS SYSDBA\'
exp \'username/password@instance AS SYSDBA\'

exp \'sys/elms AS SYSDBA\' file=dptmss01_full_sysdba.exp,  full=y, log=dptmss01_full_sysdba.log, compress=n

Seems to Work:
exp \'/ AS SYSDBA\' file=dptmss01_full_sysdba.exp,  full=y, log=dptmss01_full_sysdba.log, compress=n

The Export utility provides four modes of export:
1) Full
2) User (Owner)
3) Table
4) Tablespace

Table 1-1 Objects Exported and Imported in Each Mode

ObjectTable ModeUser ModeFull Database ModeTablespace Mode
Analyze cluster No Yes Yes No
Analyze tables/statistics Yes Yes Yes Yes
Application contexts No No Yes No
Auditing information Yes Yes Yes No
B-tree, bitmap, domain, functional indexes Yes Yes Yes Yes
Cluster definitions No Yes Yes Yes
Column and table comments Yes Yes Yes Yes
Database links No Yes Yes No
Default roles No No Yes No
Dimensions No Yes Yes No
Directory aliases No No Yes No
External tables (without data) Yes Yes Yes No
Foreign function libraries No Yes Yes No
Indexes ownerd by users other than table owner Yes (Privileged users only) Yes Yes Yes
Index types No Yes Yes No
Java resources and classes No Yes Yes No
Job queues No Yes Yes No
Nested table data Yes Yes Yes Yes
Object grants Yes (Only for tables and indexes) Yes Yes Yes
Object type definitions used by table Yes Yes Yes Yes
Object types No Yes Yes No
Operators No Yes Yes No
Password history No No Yes No
Postinstance actions and objects No No Yes No
Postschema procedural actions and objects No Yes Yes No
Posttable actions Yes Yes Yes Yes
Posttable procedureal actions and objects Yes Yes Yes Yes
Preshema procedural objects and actions No Yes Yes No
Pretable actions Yes Yes Yes Yes
Pretable procedural actions Yes Yes Yes Yes
Private synonyms No Yes Yes No
Procedural objects No Yes Yes No
Profiles No No Yes No
Public synonyms No No Yes No
Referential integrity constraints Yes Yes Yes No
Refresh groups No Yes Yes No
Resource costs No No Yes No
Role grants No No Yes No
Roles No No Yes No
Rollback segment definitions No No Yes No
Security policies for table Yes Yes Yes Yes
Sequence numbers No Yes Yes No
Snapshot logs No Yes Yes No
Snapshots and materialized views No Yes Yes No
System privilege grants No No Yes No
Table constraints (primary, unique, check) Yes Yes Yes Yes
Table data Yes Yes Yes No
Table definitions Yes Yes Yes Yes
Tablespace definitions No No Yes No
Tablespace quotas No No Yes No
Triggers Yes Yes Yes Yes
Triggers owned by other users Yes (Privileged users only) No No No
User definitions No No Yes No
User proxies No No Yes No
User views No Yes Yes No
User-stored procedures, packages, and functions No Yes Yes No
Note:
A full export does not export triggers owned by schema SYS.
You must manually re-create SYS triggers wither before or after the full import.
Oracle Corporation recommends that you re-create them after the import 
in case they define actions that would impede progress of the import.

Parameters:
compress (y)
consistent (n)
constraints (y)
direct (n)
file (expdat.dmp)
full (n)
grants (y)
indexes (y)
log (none)
owner (none)
parfile (none)
rows (y)
statistics (ESTIMATE)
tables (none)
tablespace (none)
triggers (y)

Certain parameters can conflict with each other.

Exit Codes:
EX_SUCC		Export terminated successfully without warnings
EX_OKWARN	Export terminated successfully with warnings
EX_FAIL		Export terminated unsuccessfully

Unix
EX_SUCC		0
EX_OKWARN	0
EX_FAIL		1