#SAP HANA STUDIO DATA PROVISIONING OPTIONS MANUAL#
Afterwards the current records of the table are loaded to the table on the HANA database.Ĭreates the table in the HANA target schema based on the strucuture on the source system (including manual defined structural changes). If the table already exist, it will be dropped and recreated. If the table already exist, it will be dropped and recreated.Action is not available in the HANA data provisioning UI.Ĭreates the table in the HANA target schema based on the strucuture on the source system (including manual defined structural changes). Start Replicate Process (without initial load prerequisite: delta recording has been activated before)Ĭreates the table in the HANA target schema based on the strucuture on the source system (including manual defined structural changes). Resume/Continue Replication (only possible for tables suspended before)Īctivate Delta Recording (activate trigger without starting replication) Suspend/Pause Replication (only possible for tables with replication in process) Stop Load or Replication (also if status still on scheduled) Start Replication (includes the initial load)
#SAP HANA STUDIO DATA PROVISIONING OPTIONS CODE#
The following data provisioning actions are available: Action Code Hostname of the Source System (CI_HOST) can be derived from table “SYS_REPL”.”RS_REPLICATION_COMPONENTS” field CI_HOST. Source System ID (SID) can be derived from table “SYS_REPL”.”RS_REPLICATION_COMPONENTS” field SID.
(space/D = Drop Table, T = Truncate Table, N = Keep Table SLT behaviour for target table in case of reload Table Type (space = COLUMN, ROW, HISTORY_COLUMN) Version DMIS 2011 SP4 / DMIS 2010 SP9 (or higher)ĭata provisioning order ID (not yet used) Version of LT Replication Server, the structure of table RS_ORDER looks different in the target schema. To start a data provisioning via SQL in HANA studio the following record has to be inserted into table RS_ORDER in the respective schema. Therefore RS_ORDER contains only those data provisioning requests, which are not yet handeld by the SAP LT Replication Server. In case of new entries, the requested action will be processed and the record will be deleted from RS_ORDER. The master job of the respective configuration permanently checks table RS_ORDER for new entries. All data provisioning requests for a certain schema will be added to table RS_ORDER. This table is cerated by the SAP LT Replication Server in the corresponding schema, when a new configuration is defined in the SLT configuration and monitoring dashboard. The communication between the HANA Studio and the SAP LT Replication Server is handled via table RS_ORDER. Start data provisioning via SQL in HANA Studio If a new table will be created on the source, you can start the replication for this tables by following this How To. Also when you replicate from a non-SAP source system – the Metadata information about available tables will not updated (only one time loaded to HANA). Especially in the N:1 use case, only the DDIC (DD* tables) information for the latest connected target are available at the Data Provisioning UI. Due to several reasons you want to use an action which is not available in HANA Studio or you want to start data provisioning for a table which is not displayed in the data provisioning UI due to any problem.
0 kommentar(er)
