The documentation from version 39.5.17 of PLANTA project can be found in the new PLANTA Online Help.

DT346 Database instance

DI024676 License

License number

DI025404 DB instance

Database instance

DI024675 DB schema

Database schema for which a database access is to be set up

See also: DB schema

DI025152 DB schema

Name of the DB schema

DI024860 DBMS

Database management system

Values

  • 000002 - ORACLE database
  • 000004 - MS SQL server database

DI025156 DBMS

Name of the DBMS

DI024903 Active

Values

  • Unchecked: DB instance is not activated - inactive
  • Checked: DB instance is activated - active

DI024906 Archive

Values

  • Unchecked: DB instance is no archive DB
  • Checked: DB instance is an archive DB

DI025786 Language

Language of the database instance overrides other language settings

  • e.g. user language

DI024687 Name

DI024723 Path

For SQL data bases e.g. database name ORACLE_SID

DI024724 Name

For SQL databases e.g. database name ORACLE_SID

DI024729 Connect string

For SQL databases normally by clicking on the Copy Connect String From Template button. Exception: in special cases manual input after consulting PLANTA.

Further use (in preparation):

  • Protocol = tcp
  • Host = 192.168.121.2
  • Port = 25005
  • Path = /u/db/dnew
  • Name = P01B
  • this generates the connect string:
    • tcp:192.168.121.2:25005:/u/db/dnew/P01B

DI025151 Connect string template

DI024737 Codepage

Specifies the character set used in the case of an external SQL database

DI024728 Schema file name

File name for the schema file

DI024725 User

For SQL databases: the schema name (= user)

DI024726 Password 1

For SQL databases: the user’s password

DI024727 Password 2

Always like Password 1

DI025155 DBIF

Database interface; dependent on the DBMS used

No entry option for the user

Values

  • 2 = Oracle
  • 4 = MS-SQL

DI024732 Open only if needed

Open only when required.

This function is in development.

DI024735 NULL date behavior

From DB 39.5.0

The parameter is deactivated and is no longer used

Up to DB 39.5.0

For SQL databases only: When this parameter is J, NULL is saved in the SQL database when the date field is blank. When this parameter is N, the number 0 is saved in the SQL database when the date field is blank.

DI024736 Access prot. type

The type of access protection can be specified separately for each database instance.

The new type of protection becomes effective the next time the user logs in.

Values

  • 0: No access protection (default)
  • 1: Owner-based
  • 2: ACR based (not used in 38 releases)

Details of the access rights for a data record are entered when it is created. They can be subsequently changed by system manager in special data protection modules.

DI024730 Def.- tablespace tab.

Default tablespace tables

  • Here, a location deviating from the PLANTA presets (DATA) is defined for tables.

Information

  • For databases, a tablespace describes the storage location to which tables, indexes and other data objects are written.
  • There are generally 4 types of tablespaces to be distinguished.
  • Regular tablespaces are tables and indexes.
  • They are definitions under the DBMS ORACLE.

DI024731 Def.-Tablespace Ind.

Default tablespace indices

A tablespace for indexes that deviates from the PLANTA presets (INDEX) is defined here.

DI027421 Relationship check

From S 39.5.0

Note
  • The DI is no longer used from version S 39.5.0.

Up to S 39.5.0

By activating the checkbox, the relationship check for this DB instance is started upon saving. It checks for data corruptions.

Details

  • A file with the following structure is created:
    • relation_check_“SchemaNameQ1-7B“.chk
    • Example: relation_check_Q1B.chk
  • This file is stored in the PPMS work directory.
  • The ASCII file created can be viewed in a text editor (e.g. Notepad).

Note

DI026343 Consistency check

Note

         PLANTA project









 
  • Suche in Topic-Namen

  • Suche in Topic-Inhalten
This site is powered by the TWiki collaboration platform Powered by Perl