本文主要介绍“在分析数据库中做了哪些操作”。在日常操作中，我相信很多人对分析数据库中做过哪些操作有疑问。边肖查阅了各种资料，整理出简单易用的操作方法，希望能帮助大家解答“分析数据库都做了哪些操作”的疑惑！接下来，请和边肖一起学习！
因为数据库没有打开到nomount状态，所以数据库不能打开到10046，所以我们只能通过后台日志知道数据库做了哪些操作。
执行命令分配内存(此系统内存分配不使用大页面)，内存页面大小为4k。
2020-01-24t 09:24333 3333 3333 3333 343 343 343 343 343 343 343 343 343 343 343 343 343 343 343 343 343 343 343 344
开始活动状态(正常)(OSid:12978)
2020-01-24t 09:24333 3333 3333 333 333 333 333 333 333 333 333 333 333 333 333 333 333 333 333 333 333 333 333 333 3
****************************************************
/dev/shmwillbeused for creating SGA
Larpagewillnotused未使用。只有标准4 kpageswillused将系统资源转储为SGA。
****************************************************
2020-01-24t 09:24333 3333 3333 3333 343 343 343 343 343 343 343 343 343 343 343 343 343 343 343 343 343 343 344 344
**********************************************************************
2020-01-24t 09:24333 3333 3333 3333 3333 343 343 343 343 343 343 343 343 343 343 343 343 343 343 343 343 344 343 34
然后根据系统/etc/security/limits.conf配置分配为共享全局资源(SGA)而获取的DumpsystemResourcesacquired。
2020-01-24t 09:24333 3333 3333 3333 3333 343 343 343 343 343 343 343 343 343 343 343 343 343 343 343 343 343 344 34
Perprocesssystemmemlock(软)限制=3072M
2020-01-24t 09:24333 33333 3333 3333 3333 343 343 343 343 343 343 343 343 343 343 343 343 343 343 343 343 344 344 3
期望的进程系统锁(软)限制锁
实例内存中的axsharedglobalara(SGA):792m
2020-01-24t 09:24333 3333 3333 3333 3333 343 343 343 343 343 343 343 343 343 343 343 343 343 343 343 343 344 343 34
available systemapagesizes :
4K，2048K
2020-01-24t 09:24333 3333 3333 3333 3333 3333 3333 333 333 333 333 333 333 333 333 333 333 333 333 333 333 333 333
supported systemapagesize :
page sizeavailable _ page sexcepted _ page salloped _ page serror
4k配置202757202757无
2020-01-24t 09:24333 3333 3333 3333 3333 343 343 343 343 343 343 343 343 343 343 343 343 343 343 343 343 343 343 34
原因不支持某些系统移情：
2048k-动态分配和freememoryregions区域读取CPU信息。
2020-01-24t 09:24333 3333 3333 3333 343 343 343 343 343 343 343 343 343 343 343 343 343 343 343 343 343 343 344 344
******************
****************************************************
2020-01-24T09:24:30.963798-05:00
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
2020-01-24T09:24:31.028811-05:00
Initial number of CPU is 2
Number of processor cores in the system is 2
Number of processor sockets in the system is 1
环境校验
Capability Type : Network capabilities requested : 7 detected : 0 Simulated : 0 Capability Type : Runtime Environment capabilities requested : 400000FF detected : 40000000 Simulated : 0 Capability Type : Engineered Systems capabilities requested : 7 detected : 0 Simulated : 0 Capability Type : Database Test capabilities requested : 3 detected : 0 Simulated : 0
读取参数文件
Using LOG_ARCHIVE_DEST_1 parameter default value as /u01/app/oracle/product/19.3.0/dbhome_1/dbs/arch Autotune of undo retention is turned on. IMODE=BR ILAT =51 LICENSE_MAX_USERS = 0 SYS auditing is enabled NOTE: remote asm mode is local (mode 0x1; from cluster type) NOTE: Using default ASM root directory ASM NOTE: remote asm mode is local (mode 0x1; from cluster type) NOTE: Cluster configuration type = NONE [2] Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production Version 19.3.0.0.0. ORACLE_HOME: /u01/app/oracle/product/19.3.0/dbhome_1 System name: Linux Node name: node1 Release: 3.10.0-957.el7.x86_64 Version: #1 SMP Thu Oct 4 20:48:51 UTC 2018 Machine: x86_64 Using parameter settings in server-side spfile /u01/app/oracle/product/19.3.0/dbhome_1/dbs/spfileorcl.ora System parameters with non-default values: processes = 300 nls_language = "AMERICAN" nls_territory = "AMERICA" memory_target = 792M control_files = "/oradata/ORCL/control01.ctl" control_files = "/oradata/ORCL/control02.ctl" db_block_size = 8192 compatible = "19.0.0" undo_tablespace = "UNDOTBS1" db_securefile = "PREFERRED" remote_login_passwordfile= "EXCLUSIVE" dispatchers = "(PROTOCOL=TCP) (SERVICE=orclXDB)" local_listener = "LISTENER_ORCL" audit_trail = "NONE" db_name = "orcl" open_cursors = 300 diagnostic_dest = "/u01/app/oracle"
开始启动各部分进程
2020-01-24T09:24:31.719373-05:00 ============================================================ NOTE: PatchLevel of this instance 0 ============================================================ WARNING: Invalid value for listener related parameter MIXED LISTENER 2020-01-24T09:24:31.962206-05:00 ORA-00141: all addresses specified for parameter LOCAL_LISTENER are invalid ORA-00132: syntax error or unresolved network name 'LISTENER_ORCL' Starting background process PMON 2020-01-24T09:24:32.059335-05:00 PMON started with pid=2, OS id=13012 Starting background process CLMN 2020-01-24T09:24:32.130665-05:00 CLMN started with pid=3, OS id=13014 Starting background process PSP0 2020-01-24T09:24:32.226568-05:00 PSP0 started with pid=4, OS id=13016 Starting background process VKTM 2020-01-24T09:24:33.424618-05:00 VKTM started with pid=5, OS id=13019 at elevated (RT) priority 2020-01-24T09:24:33.443572-05:00 Starting background process GEN0 2020-01-24T09:24:33.457207-05:00 VKTM running at (1)millisec precision with DBRM quantum (100)ms Starting background process MMAN 2020-01-24T09:24:33.526550-05:00 GEN0 started with pid=6, OS id=13024 2020-01-24T09:24:33.594270-05:00 MMAN started with pid=7, OS id=13026 Starting background process GEN1 2020-01-24T09:24:33.846502-05:00 GEN1 started with pid=9, OS id=13030_13031 Starting background process DIAG 2020-01-24T09:24:33.914542-05:00 DIAG started with pid=11, OS id=13033 Starting background process OFSD 2020-01-24T09:24:34.021251-05:00 OFSD started with pid=12, OS id=13035_13036 Starting background process DBRM 2020-01-24T09:24:34.029524-05:00 Oracle running with ofslib:'Oracle File Server Library' version=2 2020-01-24T09:24:34.072386-05:00 DBRM started with pid=8, OS id=13038 Starting background process VKRM 2020-01-24T09:24:34.148547-05:00 VKRM started with pid=14, OS id=13040 Starting background process SVCB 2020-01-24T09:24:34.206158-05:00 SVCB started with pid=15, OS id=13042 Starting background process PMAN 2020-01-24T09:24:34.274700-05:00 PMAN started with pid=16, OS id=13044 Starting background process DIA0 2020-01-24T09:24:34.357435-05:00 DIA0 started with pid=17, OS id=13046 Starting background process DBW0 2020-01-24T09:24:34.483648-05:00 Starting background process LGWR 2020-01-24T09:24:34.483685-05:00 DBW0 started with pid=18, OS id=13048 Starting background process CKPT 2020-01-24T09:24:34.547257-05:00 LGWR started with pid=19, OS id=13051 2020-01-24T09:24:34.625889-05:00 CKPT started with pid=20, OS id=13053 2020-01-24T09:24:34.708849-05:00 LGWR slave LG00 created with pid=21, OS pid=13055 Starting background process SMON 2020-01-24T09:24:34.771650-05:00 SMON started with pid=22, OS id=13057 LGWR slave LG01 created with pid=23, OS pid=13059 Starting background process SMCO Starting background process RECO 2020-01-24T09:24:34.910826-05:00 SMCO started with pid=24, OS id=13061 2020-01-24T09:24:34.981554-05:00 RECO started with pid=25, OS id=13063 Starting background process LREG 2020-01-24T09:24:35.115737-05:00 LREG started with pid=27, OS id=13067 Starting background process PXMN 2020-01-24T09:24:35.253859-05:00 PXMN started with pid=29, OS id=13071 Starting background process FENC 2020-01-24T09:24:35.321431-05:00 FENC started with pid=30, OS id=13073 Starting background process MMON 2020-01-24T09:24:35.379970-05:00 MMON started with pid=31, OS id=13075 Starting background process MMNL 2020-01-24T09:24:35.417133-05:00 starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'... 2020-01-24T09:24:35.417175-05:00 MMNL started with pid=30, OS id=13077 starting up 1 shared server(s) ... 2020-01-24T09:24:35.565561-05:00 Starting background process TMON 2020-01-24T09:24:35.637575-05:00 TMON started with pid=34, OS id=13083
到此，关于“分析数据库都做了哪些操作”的学习就结束了，希望能够解决大家的疑惑。理论与实践的搭配能更好的帮助大家学习，快去试试吧！若想继续学习更多相关知识，请继续关注网站，小编会继续努力为大家带来更多实用的文章！
内容来源网络，如有侵权，联系删除，本文地址：https://www.230890.com/zhan/67441.html