What’s the relationship between schema and tablespace in Oracle Database?


What’s the relationship between schema and tablespace in Oracle Database?


There is no relationship between schemas and tablespaces: a tablespace can contain objects from different schemas, and the objects for a schema can be contained in different tablespaces.

All data stored on behalf of stored PL/SQL program units (procedures, functions, packages and triggers) resides in the SYSTEM tablespace. If you create many of these PL/SQL objects, the database administrator needs to plan for the space in the SYSTEM tablespace that these objects use.

A schema is a collection of logical structures of data, or schema objects. A schema is owned by a database user and has the same name as that user. Each user owns a single schema. Schema objects can be created and manipulated with SQL and include the following types of objects:

  • Clusters
  • Database links
  • Database triggers
  • Dimensions
  • External procedure libraries
  • Indexes and index types
  • Java classes, Java resources, and Java sources
  • Materialized views and materialized view logs
  • Object tables, object types, and object views
  • Operators
  • Sequences
  • Stored functions, procedures, and packages
  • Synonyms
  • Tables and index-organized tables
  • Views

Other types of objects are also stored in the database and can be created and manipulated with SQL but are not contained in a schema:

  • Contexts
  • Directories
  • Profiles
  • Roles
  • Tablespaces
  • Users
  • Rollback segments

Schema objects are logical data storage structures. Schema objects do not have a one-to-one correspondence to physical files on disk that store their information. However, Oracle stores a schema object logically within a tablespace of the database. The data of each object is physically contained in one or more of the tablespace’s datafiles. For some objects, such as tables, indexes, and clusters, you can specify how much disk space Oracle allocates for the object within the tablespace’s datafiles.

There is no relationship between schemas and tablespaces: a tablespace can contain objects from different schemas, and the objects for a schema can be contained in different tablespaces.

Figure 1 illustrates the relationship among objects, tablespaces, and datafiles.

Figure 1 Schema Objects, Tablespaces, and Datafiles

Figure 1 Schema Objects, Tablespaces, and Datafiles

Read more from here:



Installing python on AIX

IBM does provide the Open Source binary package Python in AIX Toolbox for Linux Applications website.


python-2.7.5 Aug 16, 2013 License RPM Source An interpreted, interactive, object-oriented programming language.


However, it does not provide the prerequisites of this RPM package. After downloading it, I tried to install it on AIX 7.1 and got the following errors.

[myAIX7.1]# rpm -i python-2.7.5-1.aix6.1.ppc.rpm
error[myAIX7.1]# failed dependencies:
 libexpat.a(libexpat.so.1) is needed by python-2.7.5-1
 libgdbm.a(libgdbm.so.3) is needed by python-2.7.5-1
 libreadline.a(libreadline.so.6) is needed by python-2.7.5-1

There is no document in IBM site which prerequisites package need to be installed first. However, I figured it out by the name of the missing LIB names. Those needed LIBs are:


And readline package will require gzip if it is not installed already.

Here are the detailed steps:

[myAIX7.1]# wget ftp://ftp.software.ibm.com/aix/freeSoftware/aixtoolbox/RPMS/ppc/expat/expat-2.0.1-2.aix5.3.ppc.rpm
[myAIX7.1]# wget ftp://ftp.software.ibm.com/aix/freeSoftware/aixtoolbox/RPMS/ppc/gdbm/gdbm-devel-1.8.3-5.aix5.2.ppc.rpm
[myAIX7.1]# wget ftp://ftp.software.ibm.com/aix/freeSoftware/aixtoolbox/RPMS/ppc/gzip/gzip-1.2.4a-10.aix5.2.ppc.rpm
[myAIX7.1]# wget ftp://ftp.software.ibm.com/aix/freeSoftware/aixtoolbox/RPMS/ppc/readline/readline-6.1-1.aix6.1.ppc.rpm
[myAIX7.1]# rpm -i expat-2.0.1-2.aix5.3.ppc.rpm
[myAIX7.1]# rpm -i gdbm-1.8.3-5.aix5.2.ppc.rpm
[myAIX7.1]# rpm -i gzip-1.2.4a-10.aix5.2.ppc.rpm
[myAIX7.1]# rpm -i readline-6.1-1.aix6.1.ppc.rpm
[myAIX7.1]# rpm -i python-2.7.5-1.aix6.1.ppc.rpm
[myAIX7.1]# rpm -qa|grep python




Supported Management Consoles for Flex Power Nodes


Flex nodes can be managed by HMC, IVM or FSM. Only one manager type can be active – dual management by FSM and HMC is not supported.

Resolving the problem

Flex POWER nodes are supported as standalone (no Management Console) or with any of the following Management Consoles: IVM, HMC, or FSM.

AIX Linux IBM i
Standalone (1) y y n (2)
IVM (1) y y y
HMC (1) y y y
FSM y y y

(1) If a FSM manages the chassis then it must manage all POWER nodes in the chassis. Dual management with FSM is not supported.
(2) IBM i requires VIOS and one of the supported MCs.

HMC Support for FlexAnnouncement

HMC Requirements

      HMC Version 7 Release 7.7.0 Service pack 2 ( or a later service pack.
      Firmware 01AF773_033 or higher recommended.
      Supported Combinations
01AF773_033 01AF773_051 01AF783_021
Version 7 Release 7.7.0 Service Pack 2 Service Pack 3
Note: HMC does not support TLS 1.2 enablement on this firmware level.
Not supported
Version 7 Release 7.8.0 Not supported. *Service Pack 0
(approved Jan/2014)
Not supported
Version 7 Release 7.9.0 Not supported. Not supported. *Supported
Version 8 Release 8.1.0 Not supported Not supported *Supported


      All power nodes at EC level 01AF773 must either be powered off or concurrently updated to 773.12 (AF773_056) or later


      to the conversion.

HMC Restrictions

      • Dual management with FSM is not supported.
      • FSM cannot manage any chassis that contains HMC managed POWER nodes.
      • Conversion of existing Nodes from FSM to HMC is supported.
      • Conversion of existing Nodes from HMC back to FSM is not supported. The partition configuration must be cleared and recreated.

Converting from FSM to HMC


      Prior to the conversion ensure the Flex Node has been powered on to standby state, or Operating state while no virtual servers were configured to auto-start, at least one time since installing node firmware 01AF773. Failure to perform an ipl to standby will result in the node going to incomplete state after the HMC connects. The HMC will not be able to work with or manage the node or any virtual servers.
      The last power on type can be found in

System Configuration > Edit Host > Power on Parameters

      A current value of User-Initiated indicates the last IPL was to standby. A current value of “Auto-Start for Auto-Recovery” indicates that the last ipl was to standby; assuming it was a normal, and not a crash related, power on IPL. If the current value is “Auto-Start Always” then it is not possible to determine if a standby IPL has been performed. The current value of all virtual server’s “Automatically start with managed system” can be checked however it may of been changed since the last power on. The value can be viewed in the GUI using
      the virtual server

Configuration > Manage Virtual Sever

      task. To view the setting for all virtual servers run the command on the target host(s):
      lssyscfg -m <host name> -r lpar -F name,lpar_id,auto_start | grep ,1$
      1. Use FSM to Un-manage the chassis
      To Unmanage the chassis see the Information Center section “Remove a Chassis”:


      Ensure you also complete the sub-section “Important: Before you unmanage a chassis, make sure that you complete the procedures that are described in Unmanaging a chassis”
      2. Remove the FSM node
      If the FSM is installed in the same chassis, the FSM node should be removed to prevent rediscovery of the chassis and nodes.
      3. Add the POWER node to the HMC(s)
      Use the “add managed System” (mksysconn command) to add the POWER node to the HMC(s).
      The password field requires the Flex Node’s password for USERID. The node authenticates against its ldap server which by default for an unmanaged chassis is CMM. If the CMM is configured to use an external LDAP server, the server must have an account of USERID.
      Add the power node to a second HMC if desired. Dual HMCs are supported; both HMCs must be at the same version an release.

IVM Requirements

    • VIOS
    • Conversion from HMC or FSM to IVM is not supported. The partition configuration must be cleared and recreated.