第1页 / 共178页
第2页 / 共178页
第3页 / 共178页
第4页 / 共178页
第5页 / 共178页
第6页 / 共178页
第7页 / 共178页
第8页 / 共178页
HANA 2.0 SP03 Tenant DB.pdf
SAP HANA Tenant Databases
Content
1 SAP HANA Tenant Databases Operations Guide
2 Overview of SAP HANA Tenant Databases
2.1 License Keys for the SAP HANA Database
2.2 Server Architecture of Tenant Databases
2.3 Scale-Out Architecture of Tenant Databases
2.4 The System Database
2.5 Cross-Database Access
2.6 Database Isolation
2.7 Administration of Tenant Databases
2.8 Database-Specific Configuration Parameters
2.9 System and Statistics Views in Tenant Database Systems
2.10 Connections for Tenant Databases
3 Updating a Single-Container System
3.1 Configuration
3.2 Security
3.3 Backup and Recovery
3.4 Landscape
3.5 Perform an Offline Update
3.6 Perform a Near-Zero Downtime Update
4 Security and Tenant Databases
4.1 Cross-Database Authorization in Tenant Databases
4.2 Restricted Features in Tenant Databases
4.3 Default Blacklisted System Properties in Tenant Databases
5 Managing Tenant Databases
5.1 Creating and Configuring Tenant Databases
5.1.1 Converting an SAP HANA System to Support Tenant Databases
5.1.1.1 Convert to Tenant Databases Using the Graphical User Interface
5.1.1.2 Convert to Tenant Databases Using the Command-Line Interface
5.1.1.3 Convert to Tenant Databases Using the Web User Interface
5.1.1.4 Parameter Reference: Converting an SAP HANA System to Support Tenant Databases
5.1.1.4.1 import_content
5.1.1.4.2 nostart
5.1.1.4.3 nostart_tenant_db
5.1.1.5 Convert a System Replication Landscape to Support Tenant Databases
5.1.1.5.1 Perform an Offline Conversion
5.1.1.5.2 Perform a Near-Zero Downtime Conversion
5.1.2 Increase the System Isolation Level
5.1.2.1 Database Isolation
5.1.2.2 File and Directory Permissions with High Isolation
5.1.2.3 Assign the OS User and Group for High Isolation
5.1.3 Decrease the System Isolation Level
5.1.3.1 Clear the OS User and Group when Decreasing Isolation
5.1.4 Create a Tenant Database
5.1.5 Start a Tenant Database
5.1.6 Stop a Tenant Database
5.1.7 Rename a Tenant Database
5.1.8 Delete a Tenant Database
5.1.9 Disable Features on a Tenant Database
5.1.10 Enable and Configure Cross-Database Access
5.1.10.1 Cross-Database Access
5.1.10.2 Workload Management and Cross-Database Queries
5.1.10.3 Troubleshooting Error Situations Related to Cross-Database Access
5.1.11 Prevent Changes to System Properties in Tenant Databases
5.1.11.1 Default Blacklisted System Properties in Tenant Databases
5.1.12 Configure HTTP(S) Access to Tenant Databases via SAP HANA XS Classic
5.1.13 Configure Host-Independent Tenant Addresses
5.1.14 Create a Fallback Snapshot
5.1.15 Reset to a Fallback Snapshot
5.1.16 Delete a Fallback Snapshot
5.1.17 Prevent the Start of a Tenant Database at System Startup
5.1.18 Copy or Move a Tenant Database Using Replication
5.1.19 Reset the SYSTEM Password of a Tenant using the Cockpit
5.2 Monitoring and Managing Tenant Databases
5.2.1 Monitoring Tenant Databases in SAP HANA Cockpit
5.2.1.1 Database Details
5.2.1.2 Service Details
5.2.1.3 Key Performance Indicators
5.2.1.4 Monitor Alerts for a Tenant Database
5.2.1.4.1 Alert Details
5.2.1.4.2 Alert Priorities
5.2.1.4.3 Alert Checker Details
5.2.1.4.4 Alert Checker Statuses
5.2.2 Add or Remove Services in a Tenant Database
5.2.3 Change the Port of a Service in a Tenant Database
5.2.4 Restrict Features Available to a Tenant Database
5.2.5 Lock Parameters Against Editing for a Tenant Database
5.2.5.1 Default Blacklisted System Properties in Tenant Databases
5.2.5.2 Unlock Blacklisted Parameters
5.2.5.3 Copy Blacklisted Parameters
5.2.6 View Diagnosis Files of an Unavailable Tenant Database
5.2.7 System and Statistics Views in Tenant Database Systems
5.3 Configuring Memory and CPU Usage for Tenant Databases
5.3.1 Define Memory Allocation Limits
5.3.1.1 SAP HANA Used Memory
5.3.1.2 Memory Sizing
5.3.1.3 Allocated Memory Pools and Allocation Limits
5.3.1.4 SAP HANA Memory Usage and the Operating System
5.3.2 Define CPU Cores Allocation Limits
5.3.2.1 Controlling CPU Consumption
5.4 Using SAP Web Dispatcher for Load Balancing with Tenant Databases
5.4.1 Virtual-Host-Based Routing
5.4.2 Configuring an External SAP Web Dispatcher for Tenant Databases
5.4.2.1 Option 1: Configuring Access to Multiple (or All) Tenant Databases Through External Web Dispatcher Only
5.4.2.2 Option 2: Configuring Access to Multiple (or All) Tenant Databases Through External Web Dispatcher and Directly
6 Copying and Moving Tenant Databases Between Systems
6.1 Copy and Move Process
6.2 Security of the Copy and Move Process
6.2.1 Disable Secure Network Communication
6.3 Preparing to Copy or Move a Tenant Database
6.3.1 Verify TLS/SSL Configuration of Internal Communication Channels
6.3.2 Set Up Trust Relationship Between Target and Source Systems
6.3.3 Open Communication From Target to Source System
6.3.4 Create Credential for Authenticated Access to Source System
6.3.5 Back Up Tenant Database
6.4 Copy a Tenant Database to Another System
6.5 Move a Tenant Database to Another System
6.6 Perform Manual Post-Copy/Move Tasks
7 SAP HANA System Replication with Tenant Databases
8 Backing Up and Recovering Tenant Databases
9 Important Disclaimer for Features in SAP HANA Platform
Important Disclaimers and Legal Information
Copyright / Legal Notice
PUBLIC
SAP HANA Platform 2.0 SPS 03
Document Version: 1.1 – 2018-10-31
SAP HANA Tenant Databases
Operations Guide
.
d
e
v
r
e
s
e
r
s
t
h
g
i
r
l
l
A
.
y
n
a
p
m
o
c
e
t
a
i
l
ffi
a
P
A
S
n
a
r
o
E
S
P
A
S
8
1
0
2
©
THE BEST RUN
Content
1
SAP HANA Tenant Databases Operations Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Overview of SAP HANA Tenant Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2
License Keys for the SAP HANA Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
2.1
Server Architecture of Tenant Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
2.2
Scale-Out Architecture of Tenant Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
2.3
The System Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.4
Cross-Database Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.5
Database Isolation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
2.6
Administration of Tenant Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.7
Database-Specific Configuration Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
2.8
2.9
System and Statistics Views in Tenant Database Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
2.10 Connections for Tenant Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3
3.1
3.2
3.3
3.4
3.5
3.6
4
4.1
4.2
4.3
5
5.1
Updating a Single-Container System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
Backup and Recovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Landscape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Perform an Offline Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Perform a Near-Zero Downtime Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
Security and Tenant Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Cross-Database Authorization in Tenant Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Restricted Features in Tenant Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
Default Blacklisted System Properties in Tenant Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Managing Tenant Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Creating and Configuring Tenant Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Converting an SAP HANA System to Support Tenant Databases. . . . . . . . . . . . . . . . . . . . . . . . .45
Increase the System Isolation Level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Decrease the System Isolation Level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Create a Tenant Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65
Start a Tenant Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Stop a Tenant Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Rename a Tenant Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Delete a Tenant Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Disable Features on a Tenant Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
2
P U B L I C
SAP HANA Tenant Databases
Content
Enable and Configure Cross-Database Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Prevent Changes to System Properties in Tenant Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Configure HTTP(S) Access to Tenant Databases via SAP HANA XS Classic. . . . . . . . . . . . . . . . . 84
Configure Host-Independent Tenant Addresses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Create a Fallback Snapshot. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Reset to a Fallback Snapshot. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Delete a Fallback Snapshot. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Prevent the Start of a Tenant Database at System Startup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Copy or Move a Tenant Database Using Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95
Reset the SYSTEM Password of a Tenant using the Cockpit. . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Monitoring and Managing Tenant Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Monitoring Tenant Databases in SAP HANA Cockpit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Add or Remove Services in a Tenant Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Change the Port of a Service in a Tenant Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Restrict Features Available to a Tenant Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Lock Parameters Against Editing for a Tenant Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
View Diagnosis Files of an Unavailable Tenant Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
System and Statistics Views in Tenant Database Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . .119
Configuring Memory and CPU Usage for Tenant Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Define Memory Allocation Limits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Define CPU Cores Allocation Limits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Using SAP Web Dispatcher for Load Balancing with Tenant Databases. . . . . . . . . . . . . . . . . . . . . . 134
Virtual-Host-Based Routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135
Configuring an External SAP Web Dispatcher for Tenant Databases. . . . . . . . . . . . . . . . . . . . . .137
Copying and Moving Tenant Databases Between Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Copy and Move Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Security of the Copy and Move Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Disable Secure Network Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Preparing to Copy or Move a Tenant Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Verify TLS/SSL Configuration of Internal Communication Channels. . . . . . . . . . . . . . . . . . . . . 157
Set Up Trust Relationship Between Target and Source Systems. . . . . . . . . . . . . . . . . . . . . . . . 159
Open Communication From Target to Source System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .161
Create Credential for Authenticated Access to Source System. . . . . . . . . . . . . . . . . . . . . . . . . 162
Back Up Tenant Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Copy a Tenant Database to Another System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .164
Move a Tenant Database to Another System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .167
Perform Manual Post-Copy/Move Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
SAP HANA System Replication with Tenant Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Backing Up and Recovering Tenant Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174
5.2
5.3
5.4
6
6.1
6.2
6.3
6.4
6.5
6.6
7
8
SAP HANA Tenant Databases
Content
P U B L I C
3
9
Important Disclaimer for Features in SAP HANA Platform. . . . . . . . . . . . . . . . . . . . . . . . . . . .175
4
P U B L I C
SAP HANA Tenant Databases
Content
1
SAP HANA Tenant Databases Operations
Guide
SAP HANA tenant databases represent the basis for multitenancy in SAP HANA. Being able to run and manage
multiple tenant databases in one SAP HANA system helps you to lower capital expenditure, simplify database
management and build multi-tenant cloud applications.
This guide covers configuration, administrative, monitoring, and other operating tasks typically performed by
the administrator of an SAP HANA system that supports tenant databases. For more information about how to
install an SAP HANA system, see the SAP HANA Server Installation and Update Guide.
Note
If you have SAP HANA options installed, review the section about tenant databases in the administration
guide of the corresponding option for additional information before proceeding. Be aware that you need
additional licenses for SAP HANA options and capabilities. For more information, see Important Disclaimer
for Features in SAP HANA Platform, Options and Capabilities.
Important SAP Notes
SAP Note Number
Title
2096000
2101244
2423367
SAP HANA Multitenant Database Containers – Additional In
formation
FAQ: SAP HANA Multitenant Database Containers
Multitenant database containers will become the standard
and only operation mode
Related Information
Important Disclaimer for Features in SAP HANA Platform [page 175]
SAP HANA Tenant Databases
SAP HANA Tenant Databases Operations Guide
P U B L I C
5
2 Overview of SAP HANA Tenant Databases
SAP HANA supports multiple isolated databases in a single SAP HANA system. These are referred to as tenant
databases.
An SAP HANA system is capable of containing more than one tenant database.
A system always has exactly one system database, used for central system administration, and any number of
tenant databases (including zero). An SAP HANA system is identified by a single system ID (SID). Databases
are identified by a SID and a database name. From the administration perspective, there is a distinction
between tasks performed at system level and those performed at database level. Database clients, such as the
SAP HANA cockpit, connect to specific databases.
All the databases share the same installation of database system software, the same computing resources, and
the same system administration. However, each database is self-contained and fully isolated with its own:
● Set of database users
● Database catalog
● Repository
● Persistence
● Backups
● Traces and logs
Although database objects such as schemas, tables, views, procedures, and so on are local to the database,
cross-database SELECT queries are possible. This supports cross-application reporting, for example.
6
P U B L I C
SAP HANA Tenant Databases
Overview of SAP HANA Tenant Databases
On-premise Deployment Using SAP HANA Tenant Databases
2.1
License Keys for the SAP HANA Database
At least one license key is required to use the SAP HANA system. This license key must be installed in the
system database. There are two kinds of license key: temporary license keys and permanent license keys.
Temporary License Keys
A temporary license key, which is valid for 90 days, is automatically installed in the system database of a new
SAP HANA system and is effective for all tenant databases. During this period, you should request and install a
permanent license key.
Permanent License Keys
You can request a permanent license key on SAP Support Portal (http://support.sap.com ) under Request a
Key. Permanent license keys are valid until the predefined expiration date. Furthermore, they specify the
SAP HANA Tenant Databases
Overview of SAP HANA Tenant Databases
P U B L I C
7
amount of memory licensed to the target SAP HANA database. Before a permanent license key expires, you
should request and apply a new permanent license key. If a permanent license key expires in the system
database, a temporary license key valid for 28 days is automatically installed. During this time, you can request
and install a new permanent license key, for example, using the SAP HANA cockpit.
License Keys for Tenant Databases
You can install permanent license keys in individual tenant databases. The license key installed in a tenant
database is valid for that database only and takes precedence over the license key installed in the system
database. If a tenant-specific license key is not installed, the system database license key is effective in the
tenant database.
Tip
The system view SYS.M_LICENSE provides tenant administrators with information on the license key
effective in their tenant database, as well as where the license key is installed: in the tenant database itself
or in the system database. System administrators can use the view SYS_DATABASES.M_LICENSE to see
the same information for all tenant databases.
Unenforced and Enforced License Keys
There are two types of permanent license key available for SAP HANA: unenforced and enforced. If an
unenforced license key is installed, the operation of SAP HANA is not affected if its memory consumption
exceeds the licensed amount of memory. However, if an enforced license is installed, the database is locked
down when the current memory consumption of SAP HANA exceeds the licensed amount of memory plus
some tolerance. If this happens, either SAP HANA needs to be restarted, or a new license key that covers the
amount of memory in use needs to be installed.
The two types of permanent license key differ from each other in the following line in the license key file:
License Key Type
Unenforced
Enforced
License Key File Entry
SWPRODUCTNAME=SAP-HANA
SWPRODUCTNAME=SAP-HANA-ENF
SWPRODUCTNAME=SAP-HANA-DEV
SWPRODUCTNAME=SAP-HANA-DIGITAL
Note
It is technically possible to install an enforced license in an SAP HANA database with a regular, unenforced
permanent license. In this case, the unenforced license key has priority. That is, if a valid unenforced license
key is found, excessive memory consumption will not result in a system lockdown. However, if one license
key expires and becomes invalid, the other one, if valid, becomes the valid license key of the instance. If the
latter is an enforced license key, then the memory consumption check is enforced.
8
P U B L I C
SAP HANA Tenant Databases
Overview of SAP HANA Tenant Databases
相关推荐
2023年江西萍乡中考道德与法治真题及答案.doc
2012年重庆南川中考生物真题及答案.doc
2013年江西师范大学地理学综合及文艺理论基础考研真题.doc
2020年四川甘孜小升初语文真题及答案I卷.doc
2020年注册岩土工程师专业基础考试真题及答案.doc
2023-2024学年福建省厦门市九年级上学期数学月考试题及答案.doc
2021-2022学年辽宁省沈阳市大东区九年级上学期语文期末试题及答案.doc
2022-2023学年北京东城区初三第一学期物理期末试卷及答案.doc
2018上半年江西教师资格初中地理学科知识与教学能力真题及答案.doc
2012年河北国家公务员申论考试真题及答案-省级.doc
2020-2021学年江苏省扬州市江都区邵樊片九年级上学期数学第一次质量检测试题及答案.doc
2022下半年黑龙江教师资格证中学综合素质真题及答案.doc
