|
|
Best Practices for Deploying TWiki Software on GlassFish Application Server Using LRW
|
|
capture-schema(1m) Application Server Utility capture-schema(1m) NAME
capture-schema - stores the database metadata (schema) in a file for use in mapping and execution SYNOPSIS
capture-schema-dburl url-username name- password password-driver a_jdbc_driver [-schemaname name] [-table tablename]* [-out filename] Stores the database metadata (schema) in a file. You can also use the Sun Java System Studio IDE to capture the database schema. Run cap- ture-schema as the same database user that owns the tables, so that the -username and -schemaname options are given the same username. Additionally, you can grant the database user running the capture-schema command the ANALYZE ANY TABLE privilege. OPTIONS
-dburl JDBC URL expected by the driver for accessing a database. -username user name for authenticating access to a database. -password password for accessing the selected database. -driver JDBC driver classname in your CLASSPATH. -schemaname name of the user schema being captured. If not specified, the default will capture metadata for all tables from all the schemas accessible to this user. Specifying this parameter is highly recommended. If more than one schema is accessible to this user, more than one table with the same name may be captured which will cause problems. -table name of the table; multiple table names can be specified. -out output target; defaults to stdout. This parameter corresponds to the schema sub-element of the sun-cmp-mapping ele- ment in the sun-cmp-mapping_1_1.dtd file. EXAMPLES
Example 1: Using capture-schema capture-schema -dburl jdbc:oracle:thin:@sadbuttrue:1521:ora817 -schemaname cantiflas -username CANTIFLAS -password enigma -driver oracle.jdbc.driver.OracleDriver asadmin(1M) Sun Java System Application Server March 2004 capture-schema(1m)
