SAP ABAP Message Class RSDA_SYB (Messages for near-line implementation for Sybase IQ)
Basic Data
Hierarchy
☛
SAP_BW (Software Component) SAP Business Warehouse
⤷
BW-WHM-DST (Application Component) Data Staging
⤷
RSDA_SYB (Package) BW Nearline connection for Sybase IQ
SAP_BW (Software Component) SAP Business Warehouse⤷
BW-WHM-DST (Application Component) Data Staging⤷
RSDA_SYB (Package) BW Nearline connection for Sybase IQ 
Attributes
| Message class |  |
RSDA_SYB |
| Short Description |  |
Messages for near-line implementation for Sybase IQ |
| Changed On |  |
20140121 |
| Last Changed At |  |
101748 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 |  001 |
DB connection &1 opened (work process &2 of server &3) | The short text describes the object sufficiently | |
| 2 | 002 |
DB connection &1 closed | The short text describes the object sufficiently | |
| 3 | 003 |
DB connection &1 is not definied in table DBCON | The short text describes the object sufficiently | |
| 4 | 004 |
SQLCode = &1: &2 &3 &4 | The short text describes the object sufficiently | |
| 5 | 005 |
Cannot open DB connection &1 (internal error), rc = &2 | The short text describes the object sufficiently | |
| 6 | 006 |
Database '&1' is not supported by implementation &2 | The short text describes the object sufficiently | |
| 7 | 007 |
&1 = &2 | The short text describes the object sufficiently | |
| 8 | 008 |
&1 &2 &3 &4 | The short text describes the object sufficiently | |
| 9 | 009 |
DB connection &1 could not be opened (work process &2 of server &3) | The short text describes the object sufficiently | |
| 10 | 010 |
Near-line Connection &1 is assigned to system &2 but actual system is &3 | The short text describes the object sufficiently | |
| 11 | 011 |
Table &1 created | The short text describes the object sufficiently | |
| 12 | 012 |
Table &1 changed, column &2 added/modified | The short text describes the object sufficiently | |
| 13 | 013 |
Join view &1 created for table &2 and &3 | The short text describes the object sufficiently | |
| 14 | 015 |
Table &1 deleted | The short text describes the object sufficiently | |
| 15 | 016 |
View &1 deleted | The short text describes the object sufficiently | |
| 16 | 017 |
Local proxy table &1 created | The short text describes the object sufficiently | |
| 17 | 018 |
Table &1 copied to table &2 | The short text describes the object sufficiently | |
| 18 | 019 |
Only &1 records from &2 original records copied from table &3 to table &4 | The short text describes the object sufficiently | |
| 19 | 020 |
Table &1 renamed into table &2 | The short text describes the object sufficiently | |
| 20 | 021 |
Data package &1 opened for writing to proxy table &2 | The short text describes the object sufficiently | |
| 21 | 022 |
&3 data records written as data package &1 in proxy table &2 | The short text describes the object sufficiently | |
| 22 | 023 |
Data package &1 closed for writing to proxy table &2 | The short text describes the object sufficiently | |
| 23 | 024 |
Near-line request &1 deleted | The short text describes the object sufficiently | |
| 24 | 025 |
Near-line request &1 already deleted | The short text describes the object sufficiently | |
| 25 | 028 |
Remote source &1 does not exist | The short text describes the object sufficiently | |
| 26 | 030 |
Virtual table &1 created for remote source &2, schema &3, table &4 | The short text describes the object sufficiently | |
| 27 | 031 |
Virtual table &1 dropped | The short text describes the object sufficiently | |
| 28 | 190 |
Table "&1": &2 partitions to be dropped and &3 partitions to be merged | The short text describes the object sufficiently | |
| 29 | 191 |
Table "&1": Partition "&2" must never be dropped | The short text describes the object sufficiently | |
| 30 | 192 |
Table "&1": Partition "&2" could not be dropped | The short text describes the object sufficiently | |
| 31 | 193 |
Table "&1": Partition "&2" successfully dropped | The short text describes the object sufficiently | |
| 32 | 194 |
Table "&1": Partition "&2" successfully merged into partition "&3" | The short text describes the object sufficiently | |
| 33 | 195 |
Mark at least one line with a proposed action | The short text describes the object sufficiently | |
| 34 | 196 |
Event &1 triggered for action &2 | The short text describes the object sufficiently | |
| 35 | 197 |
No new backup since end of copy phase. Current backup ID still &1 from &2 | The short text describes the object sufficiently | |
| 36 | 198 |
&1 seconds wait time for backup completion | The short text describes the object sufficiently | |
| 37 | 199 |
New backup with ID &1 from &2 available, copy phase ended with ID = &3 | The short text describes the object sufficiently | |
| 38 | 200 |
Number of partitions is below upper threshold &1% for all selected tables | The short text describes the object sufficiently | |
| 39 | 201 |
Number of partitions &1 exceeds upper threshold &2% for data table &3 | The short text describes the object sufficiently | |
| 40 | 202 |
Number of partitions exceeds upper threshold &1% for at least one table | The short text describes the object sufficiently | |
| 41 | 203 |
Backup currently active; using predecessor &1 of most recent backup ID &2 | The short text describes the object sufficiently | |
| 42 | 204 |
Copy phase ended with commit ID &1 | The short text describes the object sufficiently |
History
| Last changed on/by | |
20140121 | SAP |
| SAP Release Created in |
