Direct Load Materialization from Adaptive Server to HANA DB

Use this procedure to set up direct load materialization and enable replication from an Adaptive Server primary to a HANA DB replicate.

Use isql to log in to the replicate Replication Server:
```
isql -Uiuser -Pipassword -SRRS_servername
```
where:
- iuser is the subscription creator, who must have create object permission.
- ipassword is the password for iuser.
- RRS_servername is the server name of the replicate Replication Server.
At the replicate Replication Server, create the subscription:
```
1> create subscription subscription_name
2> for replication_definition
3> with replicate at dataserver.database
4> [where search_conditions]
5> without holdlock
6> direct_load

8> [user cusername password cpass]
9> go 
```
The dataserver.database must match the Replication Server connection name you use for the replicate database. If you specify cusername here, this name is used to log in to the primary database and select from the primary table. If you do not specify cusername here, iuser—the name specified in isql—is used. Make sure that the name used to log in to the primary database has necessary permission at the primary database.
Monitor the progress of the subscription materialization:
```
1> check subscription subscription_name for repdef_name
2> with replicate at replicate_dataserver.replicate_database
3> go 
```
When materialization is complete, Replication Server returns a message similar to:
```
Subscription <subscription_name> has been MATERIALIZED at the replicate.
```
When the subscription process is complete, Replication Server returns a message similar to:
```
Subscription <subscription_name> is VALID at the replicate.
```
If there is an error in the subscription process, the check subscription command returns a message similar to:
```
Subscription <subscription_name> encountered ERROR.
```
When a subscription encounters an error, look at the replicate and primary Replication Server log files to diagnose the cause, drop the subscription without purge, delete data from the replicate table, correct the error, and then recreate the subscription. See the Replication Server Troubleshooting Guide > Subscription Problems > check subscription > Materialization Status and the Replication Server Troubleshooting Guide > Subscription Problems > Materialization Problems.

See the Replication Server Reference Manual > Replication Server Commands and the Replication Server Administration Guide Volume 1 for information on configuring Replication Servers and materialization methods.