2025-06-10T12:22:11.374446Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2025-06-10T12:22:11.374580Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2025-06-10T12:22:11.375246Z 0 [Note] C:\Program Files\MySQL\MySQL Server 5.7\bin\mysqld.exe (mysqld 5.7.44) starting as process 8644 ...
2025-06-10T12:22:11.410522Z 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2025-06-10T12:22:11.412072Z 0 [Note] InnoDB: Uses event mutexes
2025-06-10T12:22:11.413399Z 0 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2025-06-10T12:22:11.414068Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.13
2025-06-10T12:22:11.415170Z 0 [Note] InnoDB: Number of pools: 1
2025-06-10T12:22:11.415794Z 0 [Note] InnoDB: Not using CPU crc32 instructions
2025-06-10T12:22:11.418489Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2025-06-10T12:22:11.427087Z 0 [Note] InnoDB: Completed initialization of buffer pool
2025-06-10T12:22:11.454740Z 0 [Note] InnoDB: Setting log file .\ib_logfile101 size to 48 MB
2025-06-10T12:22:11.494666Z 0 [Note] InnoDB: Setting log file .\ib_logfile1 size to 48 MB
2025-06-10T12:22:11.576570Z 0 [Note] InnoDB: Renaming log file .\ib_logfile101 to .\ib_logfile0
2025-06-10T12:22:11.586394Z 0 [Warning] InnoDB: New log files created, LSN=215880934830
2025-06-10T12:22:11.588609Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2025-06-10T12:22:11.590837Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 215880934924
2025-06-10T12:22:11.591282Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 215880934933
2025-06-10T12:22:11.591756Z 0 [Note] InnoDB: Database was not shutdown normally!
2025-06-10T12:22:11.592020Z 0 [Note] InnoDB: Starting crash recovery.
2025-06-10T12:22:11.606152Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=7] log sequence number 222653485451 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.606745Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.607860Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=2] log sequence number 222713124956 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.608377Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.609194Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=4] log sequence number 222715142897 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.609662Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.611404Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=5] log sequence number 222714954783 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.613848Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.615354Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=6] log sequence number 222715083974 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.615847Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.616854Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1965] log sequence number 222715083974 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.617360Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.618329Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1005] log sequence number 222714810545 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.618801Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.619850Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=45] log sequence number 222715142990 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.620418Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.621392Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=982] log sequence number 222715142990 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.621910Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.623118Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=962] log sequence number 222714343196 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.623631Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.624633Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=46] log sequence number 222715143029 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.625143Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.625994Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1220] log sequence number 222714400890 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.626543Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.627320Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=843] log sequence number 222715143029 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.627788Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.628730Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=47] log sequence number 222715143068 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.629217Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.630032Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=558] log sequence number 222715143068 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.630593Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.631394Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1217] log sequence number 221399793837 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.632011Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.632864Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1240] log sequence number 222714401592 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.633349Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.634393Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=48] log sequence number 222715143107 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.634867Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.635690Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1256] log sequence number 222715143107 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.636243Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.637227Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1007] log sequence number 222714345884 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.637933Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.638962Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=49] log sequence number 222715143146 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.639446Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.640255Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=863] log sequence number 222715143146 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.640723Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.641490Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=997] log sequence number 222714815822 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.642002Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.643780Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=50] log sequence number 222715143268 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.644362Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.645378Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=555] log sequence number 222715059439 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.646380Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.647909Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=51] log sequence number 222715143307 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.648447Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.649386Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1222] log sequence number 222715143307 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.650129Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.651210Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1228] log sequence number 222715069881 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.651787Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.653370Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=52] log sequence number 222715143346 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.653906Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.655467Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1015] log sequence number 222715143346 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.656047Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.657129Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=881] log sequence number 222714403539 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.657644Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.658800Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=53] log sequence number 222715084330 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.659365Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.660254Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1230] log sequence number 222715084330 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.660773Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.661712Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=838] log sequence number 220455553286 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.662228Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.663142Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=823] log sequence number 222715105237 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.663632Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.664560Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=54] log sequence number 222715143452 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.665098Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.666029Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=839] log sequence number 222714914283 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.666524Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.667682Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=55] log sequence number 222715084408 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.668212Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.669031Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1232] log sequence number 222715084408 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.669578Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.670682Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=442] log sequence number 222662775539 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.671207Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.672127Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1233] log sequence number 222715106226 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.672861Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.673871Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=56] log sequence number 222714988142 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.674385Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.675297Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=977] log sequence number 222714988142 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.675795Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.676754Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=862] log sequence number 222396660068 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.677261Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.678068Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1254] log sequence number 222715106889 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.678814Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.679732Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=57] log sequence number 222715143491 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.680223Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.681081Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=560] log sequence number 222715143491 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.681609Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.682608Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=841] log sequence number 220515328851 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.683123Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.684021Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1255] log sequence number 222713052180 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.684595Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.685650Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=58] log sequence number 222714908247 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.686330Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.687310Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1244] log sequence number 222714908247 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.687794Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.688799Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=855] log sequence number 222715107487 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.689308Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.690430Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=59] log sequence number 222715143530 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.690920Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.691881Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=878] log sequence number 222715143530 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.692641Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.693701Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=856] log sequence number 220380027614 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.695310Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.696780Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=459] log sequence number 222714924507 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.697316Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.698485Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=60] log sequence number 222715143608 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.699104Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.699975Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=987] log sequence number 222715143608 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.700533Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.701549Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1269] log sequence number 219552273495 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.702124Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.703536Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1014] log sequence number 222714925977 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.704131Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.705183Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=61] log sequence number 222715143647 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.705684Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.707018Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=988] log sequence number 222715143647 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.707511Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.708340Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=391] log sequence number 222715108680 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.708881Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.710134Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=62] log sequence number 222715143702 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.710661Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.711457Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=556] log sequence number 222715117692 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.711980Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.712872Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1253] log sequence number 222715143702 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.713378Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.714260Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1224] log sequence number 222001497531 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.714761Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.715570Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=63] log sequence number 222715143780 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.716271Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.717666Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=883] log sequence number 222715143780 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.718156Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.719078Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1971] log sequence number 222714945118 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.719583Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.720523Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=192] log sequence number 222715143866 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.721136Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.721975Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=989] log sequence number 222274135999 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.722488Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.723361Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1921] log sequence number 222714416260 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.723882Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.725956Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=866] log sequence number 222715143866 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.727372Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.728263Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=193] log sequence number 222715143952 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.728753Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.729626Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=979] log sequence number 222715143952 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.730109Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.731305Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=869] log sequence number 222714946074 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.731946Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.733135Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=194] log sequence number 222715144038 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.733642Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.734636Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=847] log sequence number 222714417357 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.735187Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.736038Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=981] log sequence number 222715144038 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.736533Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.737364Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=829] log sequence number 221429300362 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.737827Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.738774Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=195] log sequence number 222715144207 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.739402Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.740242Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1922] log sequence number 222714948000 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.740712Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.741524Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1258] log sequence number 222715144207 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.742032Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.742849Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=394] log sequence number 222331703460 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.743424Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.744205Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=196] log sequence number 222715144251 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.744674Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.745639Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=844] log sequence number 222715144251 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.746121Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.746998Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1946] log sequence number 216765423927 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.747497Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.748539Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=386] log sequence number 222715088849 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.749105Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.749975Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=197] log sequence number 222715144337 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.750481Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.751425Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=990] log sequence number 222715144337 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.751934Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.752790Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1947] log sequence number 222002491354 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.753285Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.754211Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1257] log sequence number 222714948494 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.754769Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.755880Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=198] log sequence number 222715144381 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.756443Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.757371Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=992] log sequence number 222715144381 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.758041Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.759408Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=419] log sequence number 222715090166 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.760006Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.761181Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=199] log sequence number 222714988502 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.761687Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.762605Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1248] log sequence number 222714988502 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.763133Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.764088Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=875] log sequence number 222715120892 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.764623Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.765947Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=200] log sequence number 222715144467 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.766472Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.767349Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1226] log sequence number 222714216589 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.767933Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.768893Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=887] log sequence number 222715144467 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.769394Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.770201Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=201] log sequence number 222715144511 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.770675Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.771455Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1247] log sequence number 222715144511 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.771936Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.772749Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=884] log sequence number 222715121937 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.773332Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.774241Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=202] log sequence number 222715144555 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.774703Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.775554Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=984] log sequence number 222715144555 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.776119Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.777089Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=980] log sequence number 222715122596 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.777555Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.778443Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=203] log sequence number 222715144599 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.779022Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.779968Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1260] log sequence number 222715144599 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.780463Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.781379Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=332] log sequence number 219128106580 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.782106Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.783008Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=356] log sequence number 222715092117 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.783486Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.784309Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=204] log sequence number 222715144643 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.784773Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.785616Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1006] log sequence number 222715144643 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.786125Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.786904Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=809] log sequence number 222715101125 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.787472Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.789025Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=205] log sequence number 222715144687 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.789583Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.791322Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1016] log sequence number 222715144687 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.791899Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.792856Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=319] log sequence number 222712792761 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.793430Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.794460Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=206] log sequence number 222715144937 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.795040Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.796049Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=399] log sequence number 222715144937 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.796571Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.797518Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=777] log sequence number 219378528936 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.798500Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.799765Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=559] log sequence number 222714058859 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.800243Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.801130Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=207] log sequence number 222714988892 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.801736Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.802546Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1004] log sequence number 222714988892 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.803014Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.804032Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1272] log sequence number 222711985094 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.804517Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.805285Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=208] log sequence number 222714988936 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.805858Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.806660Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=895] log sequence number 222714988936 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.807128Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.808048Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=551] log sequence number 222714642394 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.808535Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.809392Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=209] log sequence number 222714988980 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.809916Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.810803Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=810] log sequence number 222714988980 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.811334Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.812477Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=552] log sequence number 222711926635 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.812988Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.813987Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=210] log sequence number 222714989024 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.814539Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.815426Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=400] log sequence number 222714989024 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.815910Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.816738Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=347] log sequence number 217656486882 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.817217Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.818087Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=342] log sequence number 222714643294 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.818796Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.819941Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=211] log sequence number 222714395743 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.820409Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.821539Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=891] log sequence number 222714395743 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.822044Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.823336Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1934] log sequence number 222714960183 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.823853Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.824716Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=212] log sequence number 222714989084 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.825197Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.826170Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=403] log sequence number 222714989084 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.826687Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.827659Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1935] log sequence number 222711447188 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.828171Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.829223Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=213] log sequence number 222714989128 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.829763Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.830669Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1954] log sequence number 222714989128 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.831145Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.831923Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=976] log sequence number 222712810557 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.832391Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.833326Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=214] log sequence number 222714989172 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.833808Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.834694Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=344] log sequence number 222714989172 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.835176Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.836003Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=348] log sequence number 222714644928 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.836476Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.837514Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=215] log sequence number 222714709805 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.837997Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.838772Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1234] log sequence number 222714983060 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.839236Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.840131Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=216] log sequence number 222714709849 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.840589Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.841407Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1238] log sequence number 222714709849 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.841886Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.843191Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=373] log sequence number 222714255310 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.843712Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.844552Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=217] log sequence number 222714709893 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.845052Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.846143Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1018] log sequence number 222714709893 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.846668Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.847473Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1242] log sequence number 222713810046 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.847967Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.849093Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=218] log sequence number 222714989216 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.849575Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.850432Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=564] log sequence number 222714989216 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.850926Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.851682Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=349] log sequence number 220140462689 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.852227Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.854401Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1940] log sequence number 222714256995 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.855380Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.857186Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=219] log sequence number 222714989260 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.857728Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.858583Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=572] log sequence number 222714989260 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.859233Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.860139Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=351] log sequence number 222714665510 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.860661Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.861767Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=220] log sequence number 222714989304 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.862318Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.863498Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=345] log sequence number 222714989304 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.864013Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.865031Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1274] log sequence number 222714665731 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.865548Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.866676Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=221] log sequence number 222714989348 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.867204Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.868158Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=848] log sequence number 222714989348 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.868667Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.869794Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1223] log sequence number 220479283770 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.870280Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.871223Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1270] log sequence number 222714259864 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.871725Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.872605Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=222] log sequence number 222714989392 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.873068Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.873910Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=850] log sequence number 222714989392 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.874412Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.875367Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=324] log sequence number 222714260304 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.875846Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.876816Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1978] log sequence number 218354032373 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.877298Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.878213Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=223] log sequence number 222714989436 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.878730Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.879567Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=892] log sequence number 222714989436 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.880036Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.880981Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=423] log sequence number 222714684826 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.881492Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.882387Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=536] log sequence number 221409165067 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.882879Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.883993Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=224] log sequence number 222715084530 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.884500Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.885370Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=812] log sequence number 222715084530 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.885874Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.886711Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=354] log sequence number 222714261274 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.887194Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.888272Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=225] log sequence number 222715084574 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.888781Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.889668Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1246] log sequence number 222715084574 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.890253Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.891251Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=374] log sequence number 222099586633 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.891767Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.892964Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=867] log sequence number 222712816377 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.893490Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.894387Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=226] log sequence number 222715084618 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.895070Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.895946Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1972] log sequence number 222715084618 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.896603Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.897520Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1216] log sequence number 222712977783 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.897996Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.902239Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=227] log sequence number 222715084662 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.903561Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.904678Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=541] log sequence number 222715084662 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.905262Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.906191Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=378] log sequence number 222714091083 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.906693Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.907671Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=826] log sequence number 216545378577 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.908195Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.909083Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=228] log sequence number 222715084706 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.909775Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.911017Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=379] log sequence number 222714101525 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.911601Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.912487Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=533] log sequence number 222715084706 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.912962Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.914005Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=229] log sequence number 222715084750 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.914583Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.915425Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=381] log sequence number 222714262465 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.915916Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.916845Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=893] log sequence number 222715084750 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.917337Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.918168Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=230] log sequence number 222715084794 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.918674Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.919537Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1250] log sequence number 222715084794 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.920024Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.920886Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1218] log sequence number 222712979408 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.921389Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.922467Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=231] log sequence number 222715084854 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.922941Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.923726Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=894] log sequence number 222715084854 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.924211Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.925004Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=960] log sequence number 222714263288 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.925594Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.926436Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=232] log sequence number 222715084898 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.926899Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.927737Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=404] log sequence number 222715084898 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.928324Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.929128Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1219] log sequence number 220950621065 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.929624Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.932564Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=978] log sequence number 222714263902 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.933305Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.934333Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=233] log sequence number 222715084942 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.934937Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.936033Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1221] log sequence number 222715084942 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.936532Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.937441Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1225] log sequence number 222714125360 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.937939Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.939003Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=234] log sequence number 222714908976 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.939552Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.940437Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1243] log sequence number 222714908976 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.941032Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.941922Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1229] log sequence number 219072719837 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.942450Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.943244Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=557] log sequence number 222714993229 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.943712Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.944728Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=235] log sequence number 222715084986 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.945226Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.946248Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=836] log sequence number 222715084986 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.946720Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.947563Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=357] log sequence number 219084978649 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.948174Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.948967Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=971] log sequence number 222714141881 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.949445Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.950227Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=236] log sequence number 222714909064 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.950760Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.951590Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1021] log sequence number 222714909064 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.952088Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.953033Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=964] log sequence number 222714994361 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.953517Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.954432Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=237] log sequence number 222714909108 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.954928Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.955761Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=985] log sequence number 222714909108 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.956238Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.957217Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1241] log sequence number 222714995058 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.957705Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.958576Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=238] log sequence number 222715085030 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.959115Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.959911Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=876] log sequence number 222715085030 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.960377Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.961199Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1023] log sequence number 222711998195 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.961665Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.962554Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=239] log sequence number 222715085074 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.963161Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.963982Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=395] log sequence number 222715085074 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.964497Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.965617Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=860] log sequence number 222713018486 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.966212Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.967173Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=240] log sequence number 222715085118 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.967741Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.968630Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1974] log sequence number 222715085118 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.969139Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.970094Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=832] log sequence number 222714713398 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.970573Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.971436Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=241] log sequence number 222714909256 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.972208Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.973148Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=302] log sequence number 222714909256 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.973643Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.974626Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=834] log sequence number 222023772125 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.975187Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.976026Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=845] log sequence number 222714996289 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.976489Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.977302Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=242] log sequence number 222714186003 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.977904Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.978721Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=405] log sequence number 222714186003 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.979206Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.979973Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=886] log sequence number 222715005297 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.980557Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.981584Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=244] log sequence number 222715085162 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.982081Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.982895Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=817] log sequence number 222715085162 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.983372Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.984219Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=562] log sequence number 222714715271 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.984687Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.985653Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=245] log sequence number 222715085206 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.986155Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.986926Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=837] log sequence number 222715085206 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.987395Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.988195Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1982] log sequence number 222711940313 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.988852Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.989874Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=246] log sequence number 222715085250 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.990371Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.991219Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=851] log sequence number 222715085250 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.991700Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.992479Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=966] log sequence number 222711107900 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.992986Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.993788Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=247] log sequence number 222715085294 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.994501Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.995718Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=874] log sequence number 222714163937 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.997191Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:11.998984Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=852] log sequence number 222715085294 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:11.999485Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.000652Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=248] log sequence number 222714396855 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.001179Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.001983Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1927] log sequence number 222715007699 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.002943Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.003911Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=853] log sequence number 222714396855 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.004434Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.005548Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=249] log sequence number 222715085354 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.006102Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.006968Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=359] log sequence number 222715085354 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.007477Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.008324Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1956] log sequence number 222714725510 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.008880Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.009950Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=250] log sequence number 222714909432 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.010428Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.011195Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=833] log sequence number 222714909432 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.011655Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.012478Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=885] log sequence number 222715008593 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.012968Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.013884Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=251] log sequence number 222714186223 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.014409Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.015311Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=861] log sequence number 222714186223 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.015799Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.016660Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=407] log sequence number 222715009227 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.017148Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.017966Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=252] log sequence number 222715085398 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.018450Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.019291Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1017] log sequence number 222715085398 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.019761Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.020963Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=287] log sequence number 222713852615 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.021453Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.022496Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=253] log sequence number 222714909520 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.023384Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.024170Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=389] log sequence number 222714909520 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.024642Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.025539Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1958] log sequence number 222715010025 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.026077Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.027159Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=254] log sequence number 222715085442 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.027707Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.028591Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1251] log sequence number 222715085442 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.029131Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.030118Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=563] log sequence number 222714167044 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.031263Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.032298Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=255] log sequence number 222715085554 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.032799Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.033648Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=877] log sequence number 222714750198 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.034400Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.035336Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=256] log sequence number 222714186371 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.035873Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.036799Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=781] log sequence number 222715029910 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.037311Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.038352Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=963] log sequence number 222714186371 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.038859Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.039904Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=257] log sequence number 222714397075 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.040437Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.041290Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=975] log sequence number 222714397075 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.041850Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.042702Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=418] log sequence number 222713031494 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.043193Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.044004Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=258] log sequence number 222714909676 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.044649Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.045456Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1975] log sequence number 222714909676 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.045927Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.046770Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1960] log sequence number 222713856814 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.047255Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.048241Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=259] log sequence number 222715085598 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.048737Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.049599Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=331] log sequence number 222715085598 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.050095Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.050912Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1948] log sequence number 222712032271 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.051404Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.052265Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=260] log sequence number 222715085642 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.052742Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.053742Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1961] log sequence number 222714178298 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.054231Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.055036Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=446] log sequence number 222715085642 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.055517Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.056436Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=261] log sequence number 222715085686 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.056908Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.057703Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=986] log sequence number 222715085686 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.058185Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.059209Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=965] log sequence number 222712864847 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.061204Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.063557Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=262] log sequence number 222715085730 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.064308Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.065347Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1022] log sequence number 222715085730 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.065842Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.066777Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=842] log sequence number 222714179418 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.067296Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.068312Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=263] log sequence number 222714909912 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.068857Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.069731Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=871] log sequence number 222715034568 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.070240Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.071152Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=831] log sequence number 222714909912 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.071717Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.072830Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=264] log sequence number 222715085774 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.073355Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.074145Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=1252] log sequence number 222715085774 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.074610Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.075560Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=974] log sequence number 222713229937 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.076010Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.077040Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=265] log sequence number 222715085818 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.077638Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.078430Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=334] log sequence number 222712876474 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.078902Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.079784Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=447] log sequence number 222715085818 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.080273Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.081029Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=266] log sequence number 222714910112 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.081520Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.082286Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=835] log sequence number 222714910112 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.082903Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.083797Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=864] log sequence number 222715054435 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.084283Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.085117Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=267] log sequence number 222714910156 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.085583Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.086347Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=882] log sequence number 222714341349 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.086829Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.087653Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=824] log sequence number 222714910156 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.088140Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.089185Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=268] log sequence number 222714397531 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.089660Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.090441Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=779] log sequence number 222714397531 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.090911Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.091761Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=865] log sequence number 222714801237 is in the future! Current system log sequence number 215880934942.
2025-06-10T12:22:12.092372Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2025-06-10T12:22:12.208764Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.209228Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.209547Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.209942Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b01\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:12.210501Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.210780Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.211258Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b01/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.211841Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b01/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:12.212339Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.212615Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.213029Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.213459Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b01\wp_comments.ibd' OS error: 103
2025-06-10T12:22:12.213794Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.214123Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.214558Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b01/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.215171Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b01/wp_comments` because it could not be opened.
2025-06-10T12:22:12.215614Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.215881Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.216184Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.216612Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b01\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:12.217112Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.217386Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.217803Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b01/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.218379Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b01/wp_fbv` because it could not be opened.
2025-06-10T12:22:12.218763Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.219040Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.219337Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.219746Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b01\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:12.220137Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.220425Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.220848Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b01/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.221473Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b01/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:12.221881Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.222662Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.222961Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.223371Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b01\wp_links.ibd' OS error: 103
2025-06-10T12:22:12.223684Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.223950Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.224403Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b01/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.224955Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b01/wp_links` because it could not be opened.
2025-06-10T12:22:12.225362Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.225739Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.226094Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.226493Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b01\wp_options.ibd' OS error: 103
2025-06-10T12:22:12.226851Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.227185Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.227602Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b01/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.228209Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b01/wp_options` because it could not be opened.
2025-06-10T12:22:12.228646Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.229081Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.229404Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.229769Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b01\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:12.230138Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.230413Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.230801Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b01/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.231398Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b01/wp_postmeta` because it could not be opened.
2025-06-10T12:22:12.231764Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.232062Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.232358Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.232769Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b01\wp_posts.ibd' OS error: 103
2025-06-10T12:22:12.233162Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.233428Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.233839Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b01/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.234509Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b01/wp_posts` because it could not be opened.
2025-06-10T12:22:12.235054Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.236293Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.236698Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.237930Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b01\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:12.238424Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.238677Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.239437Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b01/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.240032Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b01/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:12.240488Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.240769Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.241038Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.241450Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b01\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:12.241778Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.242038Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.242527Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b01/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.243106Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b01/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:12.243680Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.244038Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.244445Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.244848Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b01\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:12.245520Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.245885Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.246381Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b01/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.246968Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b01/wp_termmeta` because it could not be opened.
2025-06-10T12:22:12.247504Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.247765Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.248114Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.248993Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b01\wp_terms.ibd' OS error: 103
2025-06-10T12:22:12.249559Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.249936Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.250669Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b01/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.251500Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b01/wp_terms` because it could not be opened.
2025-06-10T12:22:12.251948Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.252265Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.252544Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.253000Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b01\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:12.253445Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.253747Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.254227Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b01/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.254810Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b01/wp_usermeta` because it could not be opened.
2025-06-10T12:22:12.255227Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.255548Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.255807Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.256201Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b01\wp_users.ibd' OS error: 103
2025-06-10T12:22:12.256533Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.256784Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.257271Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b01/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.257873Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b01/wp_users` because it could not be opened.
2025-06-10T12:22:12.258341Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.258614Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.258874Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.259300Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b01\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:12.259633Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.259893Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.260349Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b01/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.260964Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b01/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:12.261544Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.261810Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.262078Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.262587Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b01\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:12.262889Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.263132Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.263598Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b01/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.264187Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b01/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:12.264589Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.264844Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.265099Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.265581Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b01\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:12.265904Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.266199Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.266617Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b01/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.267226Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b01/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:12.267603Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.267866Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.268147Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.268546Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b01\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:12.268899Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.269195Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.269609Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b01/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.270215Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b01/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:12.270666Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.270957Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.271267Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.271654Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b02\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:12.271982Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.272370Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.272802Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b02/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.273777Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b02/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:12.274202Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.275051Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.275862Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.276324Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b02\wp_comments.ibd' OS error: 103
2025-06-10T12:22:12.277263Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.277589Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.278015Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b02/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.278761Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b02/wp_comments` because it could not be opened.
2025-06-10T12:22:12.279276Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.279562Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.279851Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.280327Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b02\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:12.280646Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.280908Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.281376Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b02/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.281920Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b02/wp_fbv` because it could not be opened.
2025-06-10T12:22:12.282407Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.282684Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.283151Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.283616Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b02\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:12.283987Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.284310Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.284892Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b02/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.285535Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b02/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:12.285965Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.286270Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.286548Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.286916Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b02\wp_kbp_countdown_entry.ibd' OS error: 103
2025-06-10T12:22:12.287342Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.287601Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.287984Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b02/wp_kbp_countdown_entry`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.288697Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b02/wp_kbp_countdown_entry` because it could not be opened.
2025-06-10T12:22:12.289141Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.289702Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.289993Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.290435Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b02\wp_kbp_form_entry.ibd' OS error: 103
2025-06-10T12:22:12.290751Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.291000Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.291555Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b02/wp_kbp_form_entry`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.292467Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b02/wp_kbp_form_entry` because it could not be opened.
2025-06-10T12:22:12.293110Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.293464Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.293730Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.294111Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b02\wp_kbp_form_entrymeta.ibd' OS error: 103
2025-06-10T12:22:12.294584Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.294837Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.295441Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b02/wp_kbp_form_entrymeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.295995Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b02/wp_kbp_form_entrymeta` because it could not be opened.
2025-06-10T12:22:12.296504Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.296985Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.297388Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.297750Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b02\wp_links.ibd' OS error: 103
2025-06-10T12:22:12.298040Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.298435Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.298823Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b02/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.299438Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b02/wp_links` because it could not be opened.
2025-06-10T12:22:12.299830Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.300192Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.300794Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.301174Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b02\wp_options.ibd' OS error: 103
2025-06-10T12:22:12.301747Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.302236Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.302799Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b02/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.305448Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b02/wp_options` because it could not be opened.
2025-06-10T12:22:12.306019Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.306318Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.306688Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.307109Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b02\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:12.307432Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.307727Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.308190Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b02/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.308720Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b02/wp_postmeta` because it could not be opened.
2025-06-10T12:22:12.309222Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.309479Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.309738Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.310233Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b02\wp_posts.ibd' OS error: 103
2025-06-10T12:22:12.310604Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.310960Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.311612Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b02/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.312512Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b02/wp_posts` because it could not be opened.
2025-06-10T12:22:12.313260Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.313549Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.313928Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.314371Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b02\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:12.314731Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.315089Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.315476Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b02/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.316107Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b02/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:12.316488Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.316753Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.317205Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.317572Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b02\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:12.317972Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.318279Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.318662Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b02/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.319267Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b02/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:12.319628Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.320191Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.320573Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.321008Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b02\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:12.321317Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.321590Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.322065Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b02/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.322676Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b02/wp_termmeta` because it could not be opened.
2025-06-10T12:22:12.323165Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.323428Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.323693Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.324155Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b02\wp_terms.ibd' OS error: 103
2025-06-10T12:22:12.324502Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.324764Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.325342Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b02/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.325951Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b02/wp_terms` because it could not be opened.
2025-06-10T12:22:12.326355Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.326935Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.327276Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.327689Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b02\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:12.328129Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.328441Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.328986Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b02/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.329525Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b02/wp_usermeta` because it could not be opened.
2025-06-10T12:22:12.330034Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.330318Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.330576Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.331043Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b02\wp_users.ibd' OS error: 103
2025-06-10T12:22:12.331341Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.331645Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.332143Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b02/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.332739Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b02/wp_users` because it could not be opened.
2025-06-10T12:22:12.333172Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.333423Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.333778Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.334247Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b02\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:12.334584Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.334889Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.335319Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b02/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.335941Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b02/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:12.336340Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.336619Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.336960Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.337322Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b02\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:12.337630Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.337976Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.338425Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b02/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.339023Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b02/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:12.339392Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.339839Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.340186Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.340559Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b02\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:12.340938Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.341299Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.341749Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b02/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.342482Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b02/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:12.343010Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.343264Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.343610Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.344088Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b02\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:12.344416Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.344660Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.345212Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b02/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.345769Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b02/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:12.346242Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.346573Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.346937Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.347758Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b03\wp_actionscheduler_actions.ibd' OS error: 103
2025-06-10T12:22:12.348100Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.349400Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.351376Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b03/wp_actionscheduler_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.352123Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b03/wp_actionscheduler_actions` because it could not be opened.
2025-06-10T12:22:12.352654Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.352979Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.353401Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.353789Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b03\wp_actionscheduler_claims.ibd' OS error: 103
2025-06-10T12:22:12.354134Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.354493Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.354915Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b03/wp_actionscheduler_claims`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.355786Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b03/wp_actionscheduler_claims` because it could not be opened.
2025-06-10T12:22:12.356284Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.356570Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.356844Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.357310Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b03\wp_actionscheduler_groups.ibd' OS error: 103
2025-06-10T12:22:12.357668Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.357938Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.358476Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b03/wp_actionscheduler_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.359066Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b03/wp_actionscheduler_groups` because it could not be opened.
2025-06-10T12:22:12.359595Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.359856Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.360192Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.360593Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b03\wp_actionscheduler_logs.ibd' OS error: 103
2025-06-10T12:22:12.360915Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.361240Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.361701Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b03/wp_actionscheduler_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.362332Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b03/wp_actionscheduler_logs` because it could not be opened.
2025-06-10T12:22:12.362728Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.363019Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.363393Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.363762Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b03\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:12.364076Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.364397Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.364795Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b03/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.365421Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b03/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:12.365792Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.366060Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.366368Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.366752Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b03\wp_comments.ibd' OS error: 103
2025-06-10T12:22:12.367054Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.367371Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.367770Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b03/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.368361Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b03/wp_comments` because it could not be opened.
2025-06-10T12:22:12.368967Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.369360Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.369635Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.370083Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b03\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:12.370525Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.370820Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.371311Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b03/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.371842Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b03/wp_fbv` because it could not be opened.
2025-06-10T12:22:12.372280Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.372536Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.372807Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.373289Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b03\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:12.373637Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.373886Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.374352Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b03/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.375009Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b03/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:12.375587Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.375846Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.376104Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.376572Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b03\wp_kbp_countdown_entry.ibd' OS error: 103
2025-06-10T12:22:12.376898Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.377193Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.377640Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b03/wp_kbp_countdown_entry`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.378278Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b03/wp_kbp_countdown_entry` because it could not be opened.
2025-06-10T12:22:12.378687Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.379037Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.379660Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.380022Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b03\wp_kbp_form_entry.ibd' OS error: 103
2025-06-10T12:22:12.380757Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.381162Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.381971Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b03/wp_kbp_form_entry`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.383032Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b03/wp_kbp_form_entry` because it could not be opened.
2025-06-10T12:22:12.383639Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.384193Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.384514Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.384931Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b03\wp_kbp_form_entrymeta.ibd' OS error: 103
2025-06-10T12:22:12.385425Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.385755Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.386255Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b03/wp_kbp_form_entrymeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.386831Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b03/wp_kbp_form_entrymeta` because it could not be opened.
2025-06-10T12:22:12.387323Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.387590Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.387891Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.388311Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b03\wp_links.ibd' OS error: 103
2025-06-10T12:22:12.388629Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.388937Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.389421Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b03/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.390082Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b03/wp_links` because it could not be opened.
2025-06-10T12:22:12.390543Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.390836Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.391383Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.391854Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b03\wp_options.ibd' OS error: 103
2025-06-10T12:22:12.392232Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.392502Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.392953Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b03/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.393580Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b03/wp_options` because it could not be opened.
2025-06-10T12:22:12.394055Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.394343Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.394598Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.395089Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b03\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:12.395411Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.395660Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.396101Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b03/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.396620Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b03/wp_postmeta` because it could not be opened.
2025-06-10T12:22:12.397087Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.397519Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.397902Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.398384Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b03\wp_posts.ibd' OS error: 103
2025-06-10T12:22:12.398838Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.399152Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.399554Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b03/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.400267Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b03/wp_posts` because it could not be opened.
2025-06-10T12:22:12.400669Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.401011Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.401273Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.401646Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b03\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:12.402053Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.402320Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.402709Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b03/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.403382Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b03/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:12.403928Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.404207Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.404473Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.405001Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b03\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:12.405591Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.406007Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.406477Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b03/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.407168Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b03/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:12.407599Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.407902Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.408187Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.408575Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b03\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:12.408962Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.409233Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.409649Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b03/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.410359Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b03/wp_termmeta` because it could not be opened.
2025-06-10T12:22:12.410793Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.411111Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.411377Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.411774Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b03\wp_terms.ibd' OS error: 103
2025-06-10T12:22:12.412275Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.412647Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.413297Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b03/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.414029Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b03/wp_terms` because it could not be opened.
2025-06-10T12:22:12.414454Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.414838Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.415100Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.415618Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b03\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:12.416257Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.416533Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.416959Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b03/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.417575Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b03/wp_usermeta` because it could not be opened.
2025-06-10T12:22:12.417997Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.418344Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.418625Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.419007Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b03\wp_users.ibd' OS error: 103
2025-06-10T12:22:12.419384Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.419655Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.420097Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b03/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.420780Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b03/wp_users` because it could not be opened.
2025-06-10T12:22:12.421475Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.421882Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.422185Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.423146Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b03\wp_wc_admin_note_actions.ibd' OS error: 103
2025-06-10T12:22:12.423676Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.424048Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.424909Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b03/wp_wc_admin_note_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.426115Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b03/wp_wc_admin_note_actions` because it could not be opened.
2025-06-10T12:22:12.426717Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.426989Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.427288Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.427723Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b03\wp_wc_admin_notes.ibd' OS error: 103
2025-06-10T12:22:12.428166Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.428569Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.429059Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b03/wp_wc_admin_notes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.429788Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b03/wp_wc_admin_notes` because it could not be opened.
2025-06-10T12:22:12.430384Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.430737Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.431037Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.431468Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b03\wp_wc_category_lookup.ibd' OS error: 103
2025-06-10T12:22:12.431817Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.432145Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.432623Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b03/wp_wc_category_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.433254Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b03/wp_wc_category_lookup` because it could not be opened.
2025-06-10T12:22:12.433689Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.433959Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.434295Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.434682Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b03\wp_wc_customer_lookup.ibd' OS error: 103
2025-06-10T12:22:12.435027Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.435341Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.435757Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b03/wp_wc_customer_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.436416Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b03/wp_wc_customer_lookup` because it could not be opened.
2025-06-10T12:22:12.436967Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.437339Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.437634Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.438017Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b03\wp_wc_download_log.ibd' OS error: 103
2025-06-10T12:22:12.438400Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.438667Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.439093Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b03/wp_wc_download_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.439736Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b03/wp_wc_download_log` because it could not be opened.
2025-06-10T12:22:12.440217Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.440504Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.440787Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.441187Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b03\wp_wc_order_coupon_lookup.ibd' OS error: 103
2025-06-10T12:22:12.441559Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.441832Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.442355Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b03/wp_wc_order_coupon_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.443420Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b03/wp_wc_order_coupon_lookup` because it could not be opened.
2025-06-10T12:22:12.443852Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.444347Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.444621Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.445651Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b03\wp_wc_order_product_lookup.ibd' OS error: 103
2025-06-10T12:22:12.446357Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.446621Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.447069Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b03/wp_wc_order_product_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.447778Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b03/wp_wc_order_product_lookup` because it could not be opened.
2025-06-10T12:22:12.448290Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.448584Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.448858Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.449245Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b03\wp_wc_order_stats.ibd' OS error: 103
2025-06-10T12:22:12.449879Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.450407Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.451113Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b03/wp_wc_order_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.452042Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b03/wp_wc_order_stats` because it could not be opened.
2025-06-10T12:22:12.453035Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.453381Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.453707Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.454097Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b03\wp_wc_order_tax_lookup.ibd' OS error: 103
2025-06-10T12:22:12.454480Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.454744Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.455183Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b03/wp_wc_order_tax_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.455829Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b03/wp_wc_order_tax_lookup` because it could not be opened.
2025-06-10T12:22:12.456298Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.456591Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.456863Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.457247Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b03\wp_wc_product_meta_lookup.ibd' OS error: 103
2025-06-10T12:22:12.457680Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.458121Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.458641Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b03/wp_wc_product_meta_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.459237Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b03/wp_wc_product_meta_lookup` because it could not be opened.
2025-06-10T12:22:12.459784Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.460063Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.460386Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.460832Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b03\wp_wc_rate_limits.ibd' OS error: 103
2025-06-10T12:22:12.461234Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.461555Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.461991Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b03/wp_wc_rate_limits`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.462644Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b03/wp_wc_rate_limits` because it could not be opened.
2025-06-10T12:22:12.463055Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.463350Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.463703Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.464089Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b03\wp_wc_reserved_stock.ibd' OS error: 103
2025-06-10T12:22:12.464547Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.464810Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.465230Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b03/wp_wc_reserved_stock`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.465949Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b03/wp_wc_reserved_stock` because it could not be opened.
2025-06-10T12:22:12.466464Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.466759Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.467262Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.467703Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b03\wp_wc_tax_rate_classes.ibd' OS error: 103
2025-06-10T12:22:12.468063Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.468406Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.468835Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b03/wp_wc_tax_rate_classes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.469525Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b03/wp_wc_tax_rate_classes` because it could not be opened.
2025-06-10T12:22:12.470007Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.470296Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.470585Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.471205Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b03\wp_wc_webhooks.ibd' OS error: 103
2025-06-10T12:22:12.471586Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.471863Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.472293Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b03/wp_wc_webhooks`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.472892Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b03/wp_wc_webhooks` because it could not be opened.
2025-06-10T12:22:12.473326Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.473611Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.473884Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.474269Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b03\wp_woocommerce_api_keys.ibd' OS error: 103
2025-06-10T12:22:12.474669Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.475268Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.476227Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b03/wp_woocommerce_api_keys`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.476880Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b03/wp_woocommerce_api_keys` because it could not be opened.
2025-06-10T12:22:12.477719Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.477982Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.478503Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.479133Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b03\wp_woocommerce_attribute_taxonomies.ibd' OS error: 103
2025-06-10T12:22:12.479551Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.479824Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.480318Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b03/wp_woocommerce_attribute_taxonomies`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.481027Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b03/wp_woocommerce_attribute_taxonomies` because it could not be opened.
2025-06-10T12:22:12.481477Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.481738Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.482167Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.482671Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b03\wp_woocommerce_downloadable_product_permissions.ibd' OS error: 103
2025-06-10T12:22:12.483200Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.483473Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.484027Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b03/wp_woocommerce_downloadable_product_permissions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.484670Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b03/wp_woocommerce_downloadable_product_permissions` because it could not be opened.
2025-06-10T12:22:12.485253Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.485514Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.485777Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.486316Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b03\wp_woocommerce_log.ibd' OS error: 103
2025-06-10T12:22:12.486718Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.487023Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.487453Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b03/wp_woocommerce_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.488088Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b03/wp_woocommerce_log` because it could not be opened.
2025-06-10T12:22:12.488489Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.488789Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.489197Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.489554Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b03\wp_woocommerce_order_itemmeta.ibd' OS error: 103
2025-06-10T12:22:12.489947Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.490203Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.490596Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b03/wp_woocommerce_order_itemmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.491384Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b03/wp_woocommerce_order_itemmeta` because it could not be opened.
2025-06-10T12:22:12.491812Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.492094Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.492351Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.492710Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b03\wp_woocommerce_order_items.ibd' OS error: 103
2025-06-10T12:22:12.493122Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.493383Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.493805Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b03/wp_woocommerce_order_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.494495Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b03/wp_woocommerce_order_items` because it could not be opened.
2025-06-10T12:22:12.494998Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.495285Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.495563Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.495970Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b03\wp_woocommerce_payment_tokenmeta.ibd' OS error: 103
2025-06-10T12:22:12.496328Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.496589Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.497027Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b03/wp_woocommerce_payment_tokenmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.497621Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b03/wp_woocommerce_payment_tokenmeta` because it could not be opened.
2025-06-10T12:22:12.498127Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.498428Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.498695Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.499130Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b03\wp_woocommerce_payment_tokens.ibd' OS error: 103
2025-06-10T12:22:12.499592Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.500032Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.500626Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b03/wp_woocommerce_payment_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.501617Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b03/wp_woocommerce_payment_tokens` because it could not be opened.
2025-06-10T12:22:12.502204Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.502474Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.502738Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.503220Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b03\wp_woocommerce_sessions.ibd' OS error: 103
2025-06-10T12:22:12.503572Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.503864Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.504275Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b03/wp_woocommerce_sessions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.504875Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b03/wp_woocommerce_sessions` because it could not be opened.
2025-06-10T12:22:12.505331Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.505611Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.506034Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.506407Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b03\wp_woocommerce_shipping_zone_locations.ibd' OS error: 103
2025-06-10T12:22:12.506846Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.507122Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.507534Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b03/wp_woocommerce_shipping_zone_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.509307Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b03/wp_woocommerce_shipping_zone_locations` because it could not be opened.
2025-06-10T12:22:12.511480Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.511745Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.512136Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.512700Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b03\wp_woocommerce_shipping_zone_methods.ibd' OS error: 103
2025-06-10T12:22:12.513132Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.513393Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.513872Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b03/wp_woocommerce_shipping_zone_methods`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.514624Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b03/wp_woocommerce_shipping_zone_methods` because it could not be opened.
2025-06-10T12:22:12.515148Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.515453Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.515741Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.516181Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b03\wp_woocommerce_shipping_zones.ibd' OS error: 103
2025-06-10T12:22:12.516619Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.516888Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.517280Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b03/wp_woocommerce_shipping_zones`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.518025Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b03/wp_woocommerce_shipping_zones` because it could not be opened.
2025-06-10T12:22:12.518542Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.518824Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.519088Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.519554Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b03\wp_woocommerce_tax_rate_locations.ibd' OS error: 103
2025-06-10T12:22:12.520010Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.520274Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.520789Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b03/wp_woocommerce_tax_rate_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.521357Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b03/wp_woocommerce_tax_rate_locations` because it could not be opened.
2025-06-10T12:22:12.521880Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.522130Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.522673Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.523120Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b03\wp_woocommerce_tax_rates.ibd' OS error: 103
2025-06-10T12:22:12.523496Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.523762Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.524170Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b03/wp_woocommerce_tax_rates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.524852Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b03/wp_woocommerce_tax_rates` because it could not be opened.
2025-06-10T12:22:12.525278Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.525604Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.525872Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.526250Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b03\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:12.526645Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.526908Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.527466Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b03/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.528103Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b03/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:12.528681Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.529099Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.529423Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.529998Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b03\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:12.530320Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.530657Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.531056Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b03/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.531663Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b03/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:12.532069Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.532336Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.532720Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.533114Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b03\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:12.533486Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.533792Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.534239Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b03/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.534883Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b03/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:12.535287Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.535721Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.536022Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.536572Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b03\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:12.536961Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.537208Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.537702Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b03/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.538643Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b03/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:12.539630Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.539964Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.540292Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.540820Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b04\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:12.541192Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.541441Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.541924Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b04/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.542763Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b04/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:12.543373Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.543675Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.543980Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.544482Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b04\wp_comments.ibd' OS error: 103
2025-06-10T12:22:12.545106Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.545595Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.546370Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b04/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.547331Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b04/wp_comments` because it could not be opened.
2025-06-10T12:22:12.548228Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.548746Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.549410Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.550295Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b04\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:12.550646Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.550922Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.551409Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b04/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.551970Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b04/wp_fbv` because it could not be opened.
2025-06-10T12:22:12.552440Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.552717Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.553109Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.553594Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b04\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:12.553936Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.554224Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.554656Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b04/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.555297Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b04/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:12.555743Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.556001Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.556350Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.556745Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b04\wp_links.ibd' OS error: 103
2025-06-10T12:22:12.557126Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.557471Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.557864Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b04/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.558569Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b04/wp_links` because it could not be opened.
2025-06-10T12:22:12.558946Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.559269Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.559530Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.560068Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b04\wp_options.ibd' OS error: 103
2025-06-10T12:22:12.560438Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.560690Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.561296Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b04/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.561836Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b04/wp_options` because it could not be opened.
2025-06-10T12:22:12.562329Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.562661Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.562969Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.563461Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b04\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:12.563932Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.564311Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.564761Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b04/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.565421Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b04/wp_postmeta` because it could not be opened.
2025-06-10T12:22:12.565818Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.566071Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.566473Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.566858Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b04\wp_posts.ibd' OS error: 103
2025-06-10T12:22:12.567196Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.567512Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.567900Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b04/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.568534Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b04/wp_posts` because it could not be opened.
2025-06-10T12:22:12.568882Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.569160Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.569501Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.569941Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b04\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:12.570369Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.570633Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.571031Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b04/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.571724Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b04/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:12.572107Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.572489Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.572765Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.573159Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b04\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:12.573523Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.573796Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.574245Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b04/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.574824Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b04/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:12.575264Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.575568Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.575951Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.576548Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b04\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:12.576918Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.577196Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.577655Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b04/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.578296Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b04/wp_termmeta` because it could not be opened.
2025-06-10T12:22:12.578742Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.578995Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.579392Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.579749Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b04\wp_terms.ibd' OS error: 103
2025-06-10T12:22:12.580050Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.580413Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.580927Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b04/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.581809Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b04/wp_terms` because it could not be opened.
2025-06-10T12:22:12.582379Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.582627Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.582878Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.583642Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b04\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:12.583968Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.584331Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.584730Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b04/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.585377Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b04/wp_usermeta` because it could not be opened.
2025-06-10T12:22:12.585740Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.585986Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.586301Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.586656Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b04\wp_users.ibd' OS error: 103
2025-06-10T12:22:12.586944Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.587282Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.587995Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b04/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.588624Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b04/wp_users` because it could not be opened.
2025-06-10T12:22:12.589116Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.589384Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.589732Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.590393Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b04\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:12.590849Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.591357Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.591835Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b04/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.592650Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b04/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:12.593273Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.593608Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.593988Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.594411Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b04\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:12.594771Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.595028Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.595520Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b04/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.596093Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b04/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:12.596573Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.596844Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.597125Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.597681Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b04\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:12.598049Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.598336Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.598772Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b04/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.599378Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b04/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:12.599862Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.600290Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.600615Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.601018Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b04\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:12.601418Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.601686Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.602102Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b04/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.602727Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b04/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:12.603156Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.603454Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.603752Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.604325Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b05\wp_actionscheduler_actions.ibd' OS error: 103
2025-06-10T12:22:12.604721Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.605007Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.605513Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b05/wp_actionscheduler_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.606105Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b05/wp_actionscheduler_actions` because it could not be opened.
2025-06-10T12:22:12.606670Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.606943Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.607212Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.607666Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b05\wp_actionscheduler_claims.ibd' OS error: 103
2025-06-10T12:22:12.608057Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.608392Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.608855Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b05/wp_actionscheduler_claims`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.609540Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b05/wp_actionscheduler_claims` because it could not be opened.
2025-06-10T12:22:12.610006Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.610261Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.610624Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.611058Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b05\wp_actionscheduler_groups.ibd' OS error: 103
2025-06-10T12:22:12.611533Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.611800Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.612192Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b05/wp_actionscheduler_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.613049Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b05/wp_actionscheduler_groups` because it could not be opened.
2025-06-10T12:22:12.614079Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.614442Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.614763Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.615126Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b05\wp_actionscheduler_logs.ibd' OS error: 103
2025-06-10T12:22:12.615635Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.615881Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.616275Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b05/wp_actionscheduler_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.617059Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b05/wp_actionscheduler_logs` because it could not be opened.
2025-06-10T12:22:12.617543Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.617920Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.618308Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.618818Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b05\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:12.619152Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.619918Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.621441Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b05/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.622515Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b05/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:12.623036Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.623304Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.623651Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.624103Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b05\wp_comments.ibd' OS error: 103
2025-06-10T12:22:12.624445Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.624737Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.625156Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b05/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.625856Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b05/wp_comments` because it could not be opened.
2025-06-10T12:22:12.626305Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.626631Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.626892Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.627261Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b05\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:12.627634Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.627901Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.628313Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b05/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.629137Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b05/wp_fbv` because it could not be opened.
2025-06-10T12:22:12.629634Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.629896Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.630162Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.630672Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b05\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:12.631050Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.631340Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.631823Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b05/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.632699Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b05/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:12.633153Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.633517Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.633772Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.634129Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b05\wp_links.ibd' OS error: 103
2025-06-10T12:22:12.634476Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.634865Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.635251Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b05/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.635865Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b05/wp_links` because it could not be opened.
2025-06-10T12:22:12.636220Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.636590Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.636842Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.637197Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b05\wp_options.ibd' OS error: 103
2025-06-10T12:22:12.637609Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.637854Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.638237Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b05/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.638984Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b05/wp_options` because it could not be opened.
2025-06-10T12:22:12.639621Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.639911Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.640175Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.640650Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b05\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:12.640969Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.641231Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.641677Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b05/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.642234Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b05/wp_postmeta` because it could not be opened.
2025-06-10T12:22:12.642716Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.642973Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.643264Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.643688Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b05\wp_posts.ibd' OS error: 103
2025-06-10T12:22:12.644016Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.644345Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.644760Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b05/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.645286Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b05/wp_posts` because it could not be opened.
2025-06-10T12:22:12.645793Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.646043Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.646328Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.646760Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b05\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:12.647083Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.647412Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.647822Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b05/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.648414Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b05/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:12.648788Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.649035Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.649293Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.649753Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b05\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:12.650657Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.651428Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.651841Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b05/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.652442Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b05/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:12.652821Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.653245Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.653757Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.654440Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b05\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:12.655030Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.655351Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.655823Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b05/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.656581Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b05/wp_termmeta` because it could not be opened.
2025-06-10T12:22:12.656998Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.657253Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.657631Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.658010Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b05\wp_terms.ibd' OS error: 103
2025-06-10T12:22:12.658381Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.658733Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.659140Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b05/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.659811Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b05/wp_terms` because it could not be opened.
2025-06-10T12:22:12.660252Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.660930Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.661210Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.661709Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b05\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:12.662014Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.662411Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.662869Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b05/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.663627Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b05/wp_usermeta` because it could not be opened.
2025-06-10T12:22:12.664437Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.664723Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.664989Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.665424Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b05\wp_users.ibd' OS error: 103
2025-06-10T12:22:12.665877Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.666208Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.666714Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b05/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.667240Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b05/wp_users` because it could not be opened.
2025-06-10T12:22:12.667926Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.668200Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.668514Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.668893Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b05\wp_wc_admin_note_actions.ibd' OS error: 103
2025-06-10T12:22:12.669238Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.669701Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.670121Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b05/wp_wc_admin_note_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.670743Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b05/wp_wc_admin_note_actions` because it could not be opened.
2025-06-10T12:22:12.671170Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.671491Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.671752Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.672120Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b05\wp_wc_admin_notes.ibd' OS error: 103
2025-06-10T12:22:12.672500Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.672754Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.673145Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b05/wp_wc_admin_notes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.674011Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b05/wp_wc_admin_notes` because it could not be opened.
2025-06-10T12:22:12.674708Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.675057Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.675436Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.675830Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b05\wp_wc_category_lookup.ibd' OS error: 103
2025-06-10T12:22:12.676154Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.676561Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.677083Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b05/wp_wc_category_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.677745Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b05/wp_wc_category_lookup` because it could not be opened.
2025-06-10T12:22:12.678214Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.678532Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.678791Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.679153Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b05\wp_wc_customer_lookup.ibd' OS error: 103
2025-06-10T12:22:12.679564Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.679811Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.680257Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b05/wp_wc_customer_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.680958Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b05/wp_wc_customer_lookup` because it could not be opened.
2025-06-10T12:22:12.681558Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.681821Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.682074Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.682542Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b05\wp_wc_download_log.ibd' OS error: 103
2025-06-10T12:22:12.683746Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.684250Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.685077Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b05/wp_wc_download_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.686867Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b05/wp_wc_download_log` because it could not be opened.
2025-06-10T12:22:12.687565Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.687883Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.688274Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.688668Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b05\wp_wc_order_coupon_lookup.ibd' OS error: 103
2025-06-10T12:22:12.689020Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.689324Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.689753Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b05/wp_wc_order_coupon_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.690639Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b05/wp_wc_order_coupon_lookup` because it could not be opened.
2025-06-10T12:22:12.691499Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.691928Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.692524Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.693247Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b05\wp_wc_order_product_lookup.ibd' OS error: 103
2025-06-10T12:22:12.693864Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.694417Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.695078Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b05/wp_wc_order_product_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.696205Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b05/wp_wc_order_product_lookup` because it could not be opened.
2025-06-10T12:22:12.696914Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.697436Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.697776Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.698286Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b05\wp_wc_order_stats.ibd' OS error: 103
2025-06-10T12:22:12.698629Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.698877Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.699419Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b05/wp_wc_order_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.700181Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b05/wp_wc_order_stats` because it could not be opened.
2025-06-10T12:22:12.700682Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.700934Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.701352Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.701842Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b05\wp_wc_order_tax_lookup.ibd' OS error: 103
2025-06-10T12:22:12.702375Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.702649Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.703165Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b05/wp_wc_order_tax_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.703884Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b05/wp_wc_order_tax_lookup` because it could not be opened.
2025-06-10T12:22:12.704363Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.704634Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.705088Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.705502Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b05\wp_wc_product_meta_lookup.ibd' OS error: 103
2025-06-10T12:22:12.705898Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.706189Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.706614Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b05/wp_wc_product_meta_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.707236Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b05/wp_wc_product_meta_lookup` because it could not be opened.
2025-06-10T12:22:12.707691Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.707966Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.708272Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.708688Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b05\wp_wc_rate_limits.ibd' OS error: 103
2025-06-10T12:22:12.709091Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.709403Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.709880Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b05/wp_wc_rate_limits`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.710557Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b05/wp_wc_rate_limits` because it could not be opened.
2025-06-10T12:22:12.711016Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.711375Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.711695Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.712201Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b05\wp_wc_reserved_stock.ibd' OS error: 103
2025-06-10T12:22:12.712546Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.712792Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.713300Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b05/wp_wc_reserved_stock`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.713918Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b05/wp_wc_reserved_stock` because it could not be opened.
2025-06-10T12:22:12.714378Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.714631Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.715041Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.715482Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b05\wp_wc_tax_rate_classes.ibd' OS error: 103
2025-06-10T12:22:12.715865Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.716332Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.716757Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b05/wp_wc_tax_rate_classes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.717551Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b05/wp_wc_tax_rate_classes` because it could not be opened.
2025-06-10T12:22:12.718037Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.718454Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.718725Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.719206Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b05\wp_wc_webhooks.ibd' OS error: 103
2025-06-10T12:22:12.719653Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.719917Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.720355Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b05/wp_wc_webhooks`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.720938Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b05/wp_wc_webhooks` because it could not be opened.
2025-06-10T12:22:12.721448Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.721786Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.722077Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.722470Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b05\wp_woocommerce_api_keys.ibd' OS error: 103
2025-06-10T12:22:12.722814Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.723119Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.723566Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b05/wp_woocommerce_api_keys`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.724218Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b05/wp_woocommerce_api_keys` because it could not be opened.
2025-06-10T12:22:12.724666Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.724942Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.725291Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.725685Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b05\wp_woocommerce_attribute_taxonomies.ibd' OS error: 103
2025-06-10T12:22:12.726167Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.726471Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.726884Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b05/wp_woocommerce_attribute_taxonomies`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.727596Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b05/wp_woocommerce_attribute_taxonomies` because it could not be opened.
2025-06-10T12:22:12.728126Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.728449Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.728719Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.729170Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b05\wp_woocommerce_downloadable_product_permissions.ibd' OS error: 103
2025-06-10T12:22:12.729553Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.729800Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.730303Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b05/wp_woocommerce_downloadable_product_permissions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.730894Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b05/wp_woocommerce_downloadable_product_permissions` because it could not be opened.
2025-06-10T12:22:12.731572Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.731823Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.732147Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.732601Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b05\wp_woocommerce_log.ibd' OS error: 103
2025-06-10T12:22:12.733249Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.733563Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.733961Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b05/wp_woocommerce_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.734717Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b05/wp_woocommerce_log` because it could not be opened.
2025-06-10T12:22:12.735198Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.735458Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.735713Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.736153Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b05\wp_woocommerce_order_itemmeta.ibd' OS error: 103
2025-06-10T12:22:12.736501Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.736747Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.737182Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b05/wp_woocommerce_order_itemmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.737885Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b05/wp_woocommerce_order_itemmeta` because it could not be opened.
2025-06-10T12:22:12.738430Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.738749Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.739088Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.739498Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b05\wp_woocommerce_order_items.ibd' OS error: 103
2025-06-10T12:22:12.740037Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.740329Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.740719Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b05/wp_woocommerce_order_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.741481Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b05/wp_woocommerce_order_items` because it could not be opened.
2025-06-10T12:22:12.742136Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.742511Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.742896Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.743423Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b05\wp_woocommerce_payment_tokenmeta.ibd' OS error: 103
2025-06-10T12:22:12.743843Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.744175Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.744613Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b05/wp_woocommerce_payment_tokenmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.745398Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b05/wp_woocommerce_payment_tokenmeta` because it could not be opened.
2025-06-10T12:22:12.745954Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.746243Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.746573Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.747138Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b05\wp_woocommerce_payment_tokens.ibd' OS error: 103
2025-06-10T12:22:12.747594Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.747916Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.748847Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b05/wp_woocommerce_payment_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.749822Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b05/wp_woocommerce_payment_tokens` because it could not be opened.
2025-06-10T12:22:12.750463Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.750759Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.751281Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.751740Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b05\wp_woocommerce_sessions.ibd' OS error: 103
2025-06-10T12:22:12.752086Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.752390Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.752973Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b05/wp_woocommerce_sessions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.753609Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b05/wp_woocommerce_sessions` because it could not be opened.
2025-06-10T12:22:12.754105Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.754398Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.754670Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.755058Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b05\wp_woocommerce_shipping_zone_locations.ibd' OS error: 103
2025-06-10T12:22:12.755523Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.755834Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.756454Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b05/wp_woocommerce_shipping_zone_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.757094Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b05/wp_woocommerce_shipping_zone_locations` because it could not be opened.
2025-06-10T12:22:12.757796Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.758058Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.758395Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.758761Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b05\wp_woocommerce_shipping_zone_methods.ibd' OS error: 103
2025-06-10T12:22:12.759115Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.759461Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.759928Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b05/wp_woocommerce_shipping_zone_methods`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.760551Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b05/wp_woocommerce_shipping_zone_methods` because it could not be opened.
2025-06-10T12:22:12.760990Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.761304Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.761588Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.761945Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b05\wp_woocommerce_shipping_zones.ibd' OS error: 103
2025-06-10T12:22:12.762385Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.762812Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.763307Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b05/wp_woocommerce_shipping_zones`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.764002Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b05/wp_woocommerce_shipping_zones` because it could not be opened.
2025-06-10T12:22:12.764580Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.764868Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.765203Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.765600Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b05\wp_woocommerce_tax_rate_locations.ibd' OS error: 103
2025-06-10T12:22:12.765937Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.766570Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.767056Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b05/wp_woocommerce_tax_rate_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.767783Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b05/wp_woocommerce_tax_rate_locations` because it could not be opened.
2025-06-10T12:22:12.768282Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.768556Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.768813Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.769256Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b05\wp_woocommerce_tax_rates.ibd' OS error: 103
2025-06-10T12:22:12.769618Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.769872Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.770338Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b05/wp_woocommerce_tax_rates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.770895Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b05/wp_woocommerce_tax_rates` because it could not be opened.
2025-06-10T12:22:12.771381Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.771712Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.771991Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.772406Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b05\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:12.772797Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.773055Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.773501Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b05/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.774137Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b05/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:12.774589Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.774882Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.775241Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.775811Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b05\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:12.776207Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.776484Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.776940Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b05/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.777546Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b05/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:12.777929Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.778278Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.778537Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.778901Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b05\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:12.779316Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.779585Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.779979Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b05/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.780655Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b05/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:12.781036Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.781398Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.781731Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.782278Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_b05\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:12.782647Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.782908Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.783383Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_b05/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.783973Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_b05/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:12.784836Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.785194Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.785477Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.785871Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d01\wp_actionscheduler_actions.ibd' OS error: 103
2025-06-10T12:22:12.786304Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.786569Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.786986Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d01/wp_actionscheduler_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.787609Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d01/wp_actionscheduler_actions` because it could not be opened.
2025-06-10T12:22:12.788181Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.788657Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.788972Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.789481Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d01\wp_actionscheduler_claims.ibd' OS error: 103
2025-06-10T12:22:12.789901Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.790278Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.790720Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d01/wp_actionscheduler_claims`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.791411Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d01/wp_actionscheduler_claims` because it could not be opened.
2025-06-10T12:22:12.791829Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.792164Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.792440Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.792806Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d01\wp_actionscheduler_groups.ibd' OS error: 103
2025-06-10T12:22:12.793198Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.793452Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.793840Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d01/wp_actionscheduler_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.794456Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d01/wp_actionscheduler_groups` because it could not be opened.
2025-06-10T12:22:12.794833Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.795509Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.796103Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.796640Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d01\wp_actionscheduler_logs.ibd' OS error: 103
2025-06-10T12:22:12.797222Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.797503Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.797985Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d01/wp_actionscheduler_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.798685Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d01/wp_actionscheduler_logs` because it could not be opened.
2025-06-10T12:22:12.799307Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.799579Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.799992Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.800418Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d01\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:12.800812Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.801189Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.801633Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d01/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.802264Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d01/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:12.802754Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.803091Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.803413Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.803851Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d01\wp_comments.ibd' OS error: 103
2025-06-10T12:22:12.804176Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.804444Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.804922Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d01/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.805502Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d01/wp_comments` because it could not be opened.
2025-06-10T12:22:12.806110Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.806405Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.806808Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.807217Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d01\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:12.807608Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.807953Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.808364Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d01/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.808953Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d01/wp_fbv` because it could not be opened.
2025-06-10T12:22:12.809328Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.809591Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.810021Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.810430Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d01\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:12.810873Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.811148Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.811533Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d01/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.812150Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d01/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:12.812592Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.812910Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.813162Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.813515Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d01\wp_links.ibd' OS error: 103
2025-06-10T12:22:12.813869Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.814110Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.814491Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d01/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.815101Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d01/wp_links` because it could not be opened.
2025-06-10T12:22:12.815462Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.815808Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.816096Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.816496Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d01\wp_options.ibd' OS error: 103
2025-06-10T12:22:12.816895Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.817138Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.817536Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d01/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.818103Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d01/wp_options` because it could not be opened.
2025-06-10T12:22:12.818477Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.818821Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.819071Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.819432Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d01\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:12.819835Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.820083Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.820510Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d01/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.821229Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d01/wp_postmeta` because it could not be opened.
2025-06-10T12:22:12.821704Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.822047Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.822349Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.822822Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d01\wp_posts.ibd' OS error: 103
2025-06-10T12:22:12.823210Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.823565Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.824011Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d01/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.824551Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d01/wp_posts` because it could not be opened.
2025-06-10T12:22:12.825046Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.825295Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.825549Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.826091Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d01\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:12.826804Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.827137Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.828109Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d01/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.828959Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d01/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:12.830081Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.830871Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.831247Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.831674Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d01\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:12.832055Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.832487Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.832923Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d01/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.833551Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d01/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:12.833962Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.834339Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.834620Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.835047Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d01\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:12.835405Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.835660Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.836148Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d01/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.836811Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d01/wp_termmeta` because it could not be opened.
2025-06-10T12:22:12.837332Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.837642Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.837898Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.838478Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d01\wp_terms.ibd' OS error: 103
2025-06-10T12:22:12.838789Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.839138Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.839610Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d01/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.840279Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d01/wp_terms` because it could not be opened.
2025-06-10T12:22:12.840648Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.840895Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.841294Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.842062Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d01\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:12.842427Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.842711Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.843173Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d01/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.843700Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d01/wp_usermeta` because it could not be opened.
2025-06-10T12:22:12.844178Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.844465Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.844724Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.845159Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d01\wp_users.ibd' OS error: 103
2025-06-10T12:22:12.845555Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.845816Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.846279Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d01/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.846845Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d01/wp_users` because it could not be opened.
2025-06-10T12:22:12.847572Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.847865Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.848178Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.848561Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d01\wp_wc_admin_note_actions.ibd' OS error: 103
2025-06-10T12:22:12.848965Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.849249Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.849669Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d01/wp_wc_admin_note_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.850284Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d01/wp_wc_admin_note_actions` because it could not be opened.
2025-06-10T12:22:12.850706Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.850999Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.851279Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.851696Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d01\wp_wc_admin_notes.ibd' OS error: 103
2025-06-10T12:22:12.852063Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.852327Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.852769Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d01/wp_wc_admin_notes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.853391Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d01/wp_wc_admin_notes` because it could not be opened.
2025-06-10T12:22:12.854061Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.854347Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.854608Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.855040Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d01\wp_wc_category_lookup.ibd' OS error: 103
2025-06-10T12:22:12.855385Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.855639Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.856138Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d01/wp_wc_category_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.856683Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d01/wp_wc_category_lookup` because it could not be opened.
2025-06-10T12:22:12.857181Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.857455Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.857713Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.858193Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d01\wp_wc_customer_lookup.ibd' OS error: 103
2025-06-10T12:22:12.858753Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.859078Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.859610Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d01/wp_wc_customer_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.860700Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d01/wp_wc_customer_lookup` because it could not be opened.
2025-06-10T12:22:12.862111Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.863051Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.863315Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.863800Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d01\wp_wc_download_log.ibd' OS error: 103
2025-06-10T12:22:12.864139Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.864438Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.864860Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d01/wp_wc_download_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.865552Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d01/wp_wc_download_log` because it could not be opened.
2025-06-10T12:22:12.865983Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.866250Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.866567Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.866947Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d01\wp_wc_order_coupon_lookup.ibd' OS error: 103
2025-06-10T12:22:12.867304Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.867615Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.868030Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d01/wp_wc_order_coupon_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.868700Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d01/wp_wc_order_coupon_lookup` because it could not be opened.
2025-06-10T12:22:12.869162Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.869511Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.869786Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.870174Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d01\wp_wc_order_product_lookup.ibd' OS error: 103
2025-06-10T12:22:12.870591Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.870858Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.871344Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d01/wp_wc_order_product_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.871978Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d01/wp_wc_order_product_lookup` because it could not be opened.
2025-06-10T12:22:12.872438Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.872712Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.873016Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.873463Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d01\wp_wc_order_stats.ibd' OS error: 103
2025-06-10T12:22:12.873788Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.874040Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.874568Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d01/wp_wc_order_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.875131Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d01/wp_wc_order_stats` because it could not be opened.
2025-06-10T12:22:12.875566Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.875818Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.876077Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.876538Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d01\wp_wc_order_tax_lookup.ibd' OS error: 103
2025-06-10T12:22:12.876936Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.877187Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.877669Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d01/wp_wc_order_tax_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.878288Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d01/wp_wc_order_tax_lookup` because it could not be opened.
2025-06-10T12:22:12.878766Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.879017Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.879273Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.879736Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d01\wp_wc_product_meta_lookup.ibd' OS error: 103
2025-06-10T12:22:12.880067Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.880332Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.880777Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d01/wp_wc_product_meta_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.881440Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d01/wp_wc_product_meta_lookup` because it could not be opened.
2025-06-10T12:22:12.881900Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.882163Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.882474Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.882854Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d01\wp_wc_rate_limits.ibd' OS error: 103
2025-06-10T12:22:12.883185Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.883493Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.883912Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d01/wp_wc_rate_limits`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.884544Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d01/wp_wc_rate_limits` because it could not be opened.
2025-06-10T12:22:12.884931Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.885281Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.885640Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.886004Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d01\wp_wc_reserved_stock.ibd' OS error: 103
2025-06-10T12:22:12.886369Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.886683Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.887142Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d01/wp_wc_reserved_stock`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.887861Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d01/wp_wc_reserved_stock` because it could not be opened.
2025-06-10T12:22:12.888229Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.888555Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.888813Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.889177Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d01\wp_wc_tax_rate_classes.ibd' OS error: 103
2025-06-10T12:22:12.889677Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.890864Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.891621Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d01/wp_wc_tax_rate_classes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.893425Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d01/wp_wc_tax_rate_classes` because it could not be opened.
2025-06-10T12:22:12.894043Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.894595Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.895043Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.895454Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d01\wp_wc_webhooks.ibd' OS error: 103
2025-06-10T12:22:12.895861Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.896242Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.896762Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d01/wp_wc_webhooks`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.897381Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d01/wp_wc_webhooks` because it could not be opened.
2025-06-10T12:22:12.897893Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.898207Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.898496Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.898970Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d01\wp_woocommerce_api_keys.ibd' OS error: 103
2025-06-10T12:22:12.899341Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.899886Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.900329Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d01/wp_woocommerce_api_keys`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.900966Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d01/wp_woocommerce_api_keys` because it could not be opened.
2025-06-10T12:22:12.901750Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.902039Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.902310Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.902812Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d01\wp_woocommerce_attribute_taxonomies.ibd' OS error: 103
2025-06-10T12:22:12.903200Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.903452Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.903935Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d01/wp_woocommerce_attribute_taxonomies`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.904694Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d01/wp_woocommerce_attribute_taxonomies` because it could not be opened.
2025-06-10T12:22:12.905171Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.905429Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.905791Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.906176Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d01\wp_woocommerce_downloadable_product_permissions.ibd' OS error: 103
2025-06-10T12:22:12.906668Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.906980Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.907393Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d01/wp_woocommerce_downloadable_product_permissions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.908048Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d01/wp_woocommerce_downloadable_product_permissions` because it could not be opened.
2025-06-10T12:22:12.908527Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.908800Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.909074Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.909466Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d01\wp_woocommerce_log.ibd' OS error: 103
2025-06-10T12:22:12.909826Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.910107Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.910550Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d01/wp_woocommerce_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.911410Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d01/wp_woocommerce_log` because it could not be opened.
2025-06-10T12:22:12.911886Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.912328Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.912639Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.913028Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d01\wp_woocommerce_order_itemmeta.ibd' OS error: 103
2025-06-10T12:22:12.913383Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.913726Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.914140Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d01/wp_woocommerce_order_itemmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.914797Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d01/wp_woocommerce_order_itemmeta` because it could not be opened.
2025-06-10T12:22:12.915330Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.915631Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.915929Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.916581Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d01\wp_woocommerce_order_items.ibd' OS error: 103
2025-06-10T12:22:12.916967Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.917245Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.917776Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d01/wp_woocommerce_order_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.918400Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d01/wp_woocommerce_order_items` because it could not be opened.
2025-06-10T12:22:12.918905Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.919178Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.919473Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.919862Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d01\wp_woocommerce_payment_tokenmeta.ibd' OS error: 103
2025-06-10T12:22:12.920223Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.920513Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.920926Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d01/wp_woocommerce_payment_tokenmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.921540Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d01/wp_woocommerce_payment_tokenmeta` because it could not be opened.
2025-06-10T12:22:12.921967Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.922234Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.922911Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.923953Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d01\wp_woocommerce_payment_tokens.ibd' OS error: 103
2025-06-10T12:22:12.924309Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.924901Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.925318Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d01/wp_woocommerce_payment_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.926877Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d01/wp_woocommerce_payment_tokens` because it could not be opened.
2025-06-10T12:22:12.927365Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.927651Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.928007Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.928400Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d01\wp_woocommerce_sessions.ibd' OS error: 103
2025-06-10T12:22:12.928761Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.929042Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.929494Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d01/wp_woocommerce_sessions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.930077Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d01/wp_woocommerce_sessions` because it could not be opened.
2025-06-10T12:22:12.930580Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.930864Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.931139Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.931607Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d01\wp_woocommerce_shipping_zone_locations.ibd' OS error: 103
2025-06-10T12:22:12.932030Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.932295Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.932795Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d01/wp_woocommerce_shipping_zone_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.933415Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d01/wp_woocommerce_shipping_zone_locations` because it could not be opened.
2025-06-10T12:22:12.933999Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.934271Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.934739Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.935193Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d01\wp_woocommerce_shipping_zone_methods.ibd' OS error: 103
2025-06-10T12:22:12.935617Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.935910Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.936350Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d01/wp_woocommerce_shipping_zone_methods`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.937032Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d01/wp_woocommerce_shipping_zone_methods` because it could not be opened.
2025-06-10T12:22:12.937518Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.937811Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.938070Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.938431Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d01\wp_woocommerce_shipping_zones.ibd' OS error: 103
2025-06-10T12:22:12.938866Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.939140Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.939613Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d01/wp_woocommerce_shipping_zones`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.940190Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d01/wp_woocommerce_shipping_zones` because it could not be opened.
2025-06-10T12:22:12.940669Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.941079Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.941379Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.941784Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d01\wp_woocommerce_tax_rate_locations.ibd' OS error: 103
2025-06-10T12:22:12.942160Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.942437Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.942885Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d01/wp_woocommerce_tax_rate_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.943536Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d01/wp_woocommerce_tax_rate_locations` because it could not be opened.
2025-06-10T12:22:12.944003Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.944274Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.944572Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.944990Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d01\wp_woocommerce_tax_rates.ibd' OS error: 103
2025-06-10T12:22:12.945388Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.945765Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.946167Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d01/wp_woocommerce_tax_rates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.946803Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d01/wp_woocommerce_tax_rates` because it could not be opened.
2025-06-10T12:22:12.947509Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.947855Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.948198Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.948659Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d01\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:12.948991Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.949240Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.949734Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d01/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.950348Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d01/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:12.951148Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.951528Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.951817Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.952233Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d01\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:12.952635Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.952958Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.953510Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d01/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.954173Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d01/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:12.954661Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.954946Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.955228Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.955686Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d01\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:12.956104Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.956395Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.957789Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d01/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.959962Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d01/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:12.960421Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.960908Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.961381Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.961843Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d01\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:12.962277Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.962553Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.963125Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d01/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.963850Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d01/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:12.964392Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.964688Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.964950Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.965392Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d02\wp_actionscheduler_actions.ibd' OS error: 103
2025-06-10T12:22:12.965789Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.966046Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.966587Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d02/wp_actionscheduler_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.967222Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d02/wp_actionscheduler_actions` because it could not be opened.
2025-06-10T12:22:12.967686Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.967954Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.968276Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.968903Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d02\wp_actionscheduler_claims.ibd' OS error: 103
2025-06-10T12:22:12.969284Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.969552Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.969974Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d02/wp_actionscheduler_claims`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.970640Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d02/wp_actionscheduler_claims` because it could not be opened.
2025-06-10T12:22:12.971155Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.971472Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.971912Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.972771Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d02\wp_actionscheduler_groups.ibd' OS error: 103
2025-06-10T12:22:12.973214Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.973642Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.974222Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d02/wp_actionscheduler_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.974966Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d02/wp_actionscheduler_groups` because it could not be opened.
2025-06-10T12:22:12.975530Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.975835Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.976208Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.976627Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d02\wp_actionscheduler_logs.ibd' OS error: 103
2025-06-10T12:22:12.976964Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.977324Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.977837Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d02/wp_actionscheduler_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.978505Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d02/wp_actionscheduler_logs` because it could not be opened.
2025-06-10T12:22:12.978943Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.979297Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.979597Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.980040Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d02\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:12.980380Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.980645Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.981413Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d02/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.982085Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d02/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:12.982580Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.982838Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.983145Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.983651Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d02\wp_comments.ibd' OS error: 103
2025-06-10T12:22:12.984128Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.984418Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.984810Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d02/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.985405Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d02/wp_comments` because it could not be opened.
2025-06-10T12:22:12.985771Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.986022Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.986406Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.986768Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d02\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:12.987196Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.987479Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.987944Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d02/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.988526Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d02/wp_fbv` because it could not be opened.
2025-06-10T12:22:12.988871Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.989214Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.989488Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.989852Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d02\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:12.990259Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.990505Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.990890Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d02/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.991502Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d02/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:12.991934Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.992323Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.992609Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.992961Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d02\wp_kbp_countdown_entry.ibd' OS error: 103
2025-06-10T12:22:12.993364Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.993615Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.994003Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d02/wp_kbp_countdown_entry`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.994750Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d02/wp_kbp_countdown_entry` because it could not be opened.
2025-06-10T12:22:12.995295Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.995556Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.995931Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.996480Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d02\wp_kbp_form_entry.ibd' OS error: 103
2025-06-10T12:22:12.996813Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:12.997119Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:12.997607Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d02/wp_kbp_form_entry`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:12.998218Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d02/wp_kbp_form_entry` because it could not be opened.
2025-06-10T12:22:12.998710Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:12.998984Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:12.999317Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:12.999692Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d02\wp_kbp_form_entrymeta.ibd' OS error: 103
2025-06-10T12:22:13.000015Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.000373Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.000771Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d02/wp_kbp_form_entrymeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.001522Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d02/wp_kbp_form_entrymeta` because it could not be opened.
2025-06-10T12:22:13.001974Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.002277Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.002553Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.002964Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d02\wp_links.ibd' OS error: 103
2025-06-10T12:22:13.003324Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.003591Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.004678Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d02/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.005276Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d02/wp_links` because it could not be opened.
2025-06-10T12:22:13.005696Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.005967Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.006959Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.007361Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d02\wp_options.ibd' OS error: 103
2025-06-10T12:22:13.007797Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.008077Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.008541Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d02/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.009221Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d02/wp_options` because it could not be opened.
2025-06-10T12:22:13.009744Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.010112Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.010407Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.010780Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d02\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:13.011144Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.011452Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.011996Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d02/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.012673Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d02/wp_postmeta` because it could not be opened.
2025-06-10T12:22:13.013152Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.013440Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.013705Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.014163Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d02\wp_posts.ibd' OS error: 103
2025-06-10T12:22:13.014555Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.014832Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.015385Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d02/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.015920Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d02/wp_posts` because it could not be opened.
2025-06-10T12:22:13.016552Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.016837Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.017171Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.017571Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d02\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:13.017943Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.018339Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.018798Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d02/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.019526Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d02/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:13.019941Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.020287Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.020557Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.020938Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d02\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:13.021362Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.021628Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.022174Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d02/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.022997Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d02/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:13.023534Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.023793Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.024140Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.024559Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d02\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:13.024865Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.025190Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.025586Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d02/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.026311Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d02/wp_termmeta` because it could not be opened.
2025-06-10T12:22:13.026856Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.027267Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.027640Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.028154Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d02\wp_terms.ibd' OS error: 103
2025-06-10T12:22:13.028466Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.028730Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.029225Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d02/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.030099Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d02/wp_terms` because it could not be opened.
2025-06-10T12:22:13.030666Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.030971Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.031409Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.031792Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d02\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:13.032240Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.032553Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.032947Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d02/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.033586Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d02/wp_usermeta` because it could not be opened.
2025-06-10T12:22:13.033958Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.034336Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.034593Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.034959Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d02\wp_users.ibd' OS error: 103
2025-06-10T12:22:13.035681Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.036447Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.038154Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d02/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.040595Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d02/wp_users` because it could not be opened.
2025-06-10T12:22:13.041118Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.041401Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.041714Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.042194Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d02\wp_wc_admin_note_actions.ibd' OS error: 103
2025-06-10T12:22:13.042549Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.042816Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.043261Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d02/wp_wc_admin_note_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.043850Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d02/wp_wc_admin_note_actions` because it could not be opened.
2025-06-10T12:22:13.044885Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.045409Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.045795Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.046244Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d02\wp_wc_admin_notes.ibd' OS error: 103
2025-06-10T12:22:13.046585Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.046864Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.047416Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d02/wp_wc_admin_notes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.048043Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d02/wp_wc_admin_notes` because it could not be opened.
2025-06-10T12:22:13.048478Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.048749Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.049051Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.049471Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d02\wp_wc_category_lookup.ibd' OS error: 103
2025-06-10T12:22:13.049811Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.050113Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.050533Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d02/wp_wc_category_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.051147Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d02/wp_wc_category_lookup` because it could not be opened.
2025-06-10T12:22:13.051539Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.051832Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.052135Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.052521Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d02\wp_wc_customer_lookup.ibd' OS error: 103
2025-06-10T12:22:13.052871Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.053161Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.053574Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d02/wp_wc_customer_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.054184Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d02/wp_wc_customer_lookup` because it could not be opened.
2025-06-10T12:22:13.054566Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.054831Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.055140Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.055530Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d02\wp_wc_download_log.ibd' OS error: 103
2025-06-10T12:22:13.055863Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.056214Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.056661Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d02/wp_wc_download_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.057268Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d02/wp_wc_download_log` because it could not be opened.
2025-06-10T12:22:13.057677Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.057966Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.058285Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.058672Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d02\wp_wc_order_coupon_lookup.ibd' OS error: 103
2025-06-10T12:22:13.059054Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.059361Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.059780Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d02/wp_wc_order_coupon_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.060393Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d02/wp_wc_order_coupon_lookup` because it could not be opened.
2025-06-10T12:22:13.060844Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.061135Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.061402Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.061794Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d02\wp_wc_order_product_lookup.ibd' OS error: 103
2025-06-10T12:22:13.062265Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.062529Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.062948Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d02/wp_wc_order_product_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.063556Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d02/wp_wc_order_product_lookup` because it could not be opened.
2025-06-10T12:22:13.064023Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.064294Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.064567Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.064977Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d02\wp_wc_order_stats.ibd' OS error: 103
2025-06-10T12:22:13.065431Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.065733Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.066194Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d02/wp_wc_order_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.066756Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d02/wp_wc_order_stats` because it could not be opened.
2025-06-10T12:22:13.067222Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.067476Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.067801Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.068359Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d02\wp_wc_order_tax_lookup.ibd' OS error: 103
2025-06-10T12:22:13.069427Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.070671Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.072170Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d02/wp_wc_order_tax_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.072842Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d02/wp_wc_order_tax_lookup` because it could not be opened.
2025-06-10T12:22:13.073297Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.073596Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.073899Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.074348Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d02\wp_wc_product_meta_lookup.ibd' OS error: 103
2025-06-10T12:22:13.074730Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.075001Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.075421Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d02/wp_wc_product_meta_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.076140Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d02/wp_wc_product_meta_lookup` because it could not be opened.
2025-06-10T12:22:13.076726Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.077014Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.077302Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.077791Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d02\wp_wc_rate_limits.ibd' OS error: 103
2025-06-10T12:22:13.078122Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.078401Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.078918Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d02/wp_wc_rate_limits`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.079540Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d02/wp_wc_rate_limits` because it could not be opened.
2025-06-10T12:22:13.080045Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.080342Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.080652Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.081049Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d02\wp_wc_reserved_stock.ibd' OS error: 103
2025-06-10T12:22:13.081445Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.081763Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.082163Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d02/wp_wc_reserved_stock`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.082847Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d02/wp_wc_reserved_stock` because it could not be opened.
2025-06-10T12:22:13.083311Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.083660Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.083940Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.084323Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d02\wp_wc_tax_rate_classes.ibd' OS error: 103
2025-06-10T12:22:13.084710Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.084974Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.085390Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d02/wp_wc_tax_rate_classes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.086027Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d02/wp_wc_tax_rate_classes` because it could not be opened.
2025-06-10T12:22:13.086423Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.086720Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.086992Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.087377Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d02\wp_wc_webhooks.ibd' OS error: 103
2025-06-10T12:22:13.087890Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.088179Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.088654Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d02/wp_wc_webhooks`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.089182Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d02/wp_wc_webhooks` because it could not be opened.
2025-06-10T12:22:13.089664Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.089969Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.090231Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.090679Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d02\wp_woocommerce_api_keys.ibd' OS error: 103
2025-06-10T12:22:13.091157Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.091514Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.091953Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d02/wp_woocommerce_api_keys`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.092579Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d02/wp_woocommerce_api_keys` because it could not be opened.
2025-06-10T12:22:13.093006Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.093259Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.093623Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.094005Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d02\wp_woocommerce_attribute_taxonomies.ibd' OS error: 103
2025-06-10T12:22:13.094785Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.095084Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.095541Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d02/wp_woocommerce_attribute_taxonomies`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.096153Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d02/wp_woocommerce_attribute_taxonomies` because it could not be opened.
2025-06-10T12:22:13.096624Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.096893Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.097167Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.097580Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d02\wp_woocommerce_downloadable_product_permissions.ibd' OS error: 103
2025-06-10T12:22:13.097972Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.098233Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.098673Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d02/wp_woocommerce_downloadable_product_permissions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.099298Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d02/wp_woocommerce_downloadable_product_permissions` because it could not be opened.
2025-06-10T12:22:13.099757Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.100043Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.100316Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.100907Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d02\wp_woocommerce_log.ibd' OS error: 103
2025-06-10T12:22:13.101283Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.101587Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.102048Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d02/wp_woocommerce_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.102646Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d02/wp_woocommerce_log` because it could not be opened.
2025-06-10T12:22:13.103047Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.103316Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.103622Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.104168Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d02\wp_woocommerce_order_itemmeta.ibd' OS error: 103
2025-06-10T12:22:13.104588Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.104852Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.105259Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d02/wp_woocommerce_order_itemmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.106167Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d02/wp_woocommerce_order_itemmeta` because it could not be opened.
2025-06-10T12:22:13.106843Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.107459Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.107836Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.108234Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d02\wp_woocommerce_order_items.ibd' OS error: 103
2025-06-10T12:22:13.108647Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.108920Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.109342Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d02/wp_woocommerce_order_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.109985Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d02/wp_woocommerce_order_items` because it could not be opened.
2025-06-10T12:22:13.110439Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.110727Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.110991Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.111360Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d02\wp_woocommerce_payment_tokenmeta.ibd' OS error: 103
2025-06-10T12:22:13.111816Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.112071Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.112543Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d02/wp_woocommerce_payment_tokenmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.113123Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d02/wp_woocommerce_payment_tokenmeta` because it could not be opened.
2025-06-10T12:22:13.113587Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.113947Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.114230Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.114771Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d02\wp_woocommerce_payment_tokens.ibd' OS error: 103
2025-06-10T12:22:13.115111Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.115358Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.115875Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d02/wp_woocommerce_payment_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.116538Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d02/wp_woocommerce_payment_tokens` because it could not be opened.
2025-06-10T12:22:13.116970Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.117219Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.117590Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.117945Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d02\wp_woocommerce_sessions.ibd' OS error: 103
2025-06-10T12:22:13.118266Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.118743Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.119202Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d02/wp_woocommerce_sessions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.119991Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d02/wp_woocommerce_sessions` because it could not be opened.
2025-06-10T12:22:13.120803Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.121162Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.121461Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.121850Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d02\wp_woocommerce_shipping_zone_locations.ibd' OS error: 103
2025-06-10T12:22:13.122200Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.122569Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.123108Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d02/wp_woocommerce_shipping_zone_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.123802Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d02/wp_woocommerce_shipping_zone_locations` because it could not be opened.
2025-06-10T12:22:13.124283Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.124666Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.124942Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.125303Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d02\wp_woocommerce_shipping_zone_methods.ibd' OS error: 103
2025-06-10T12:22:13.125810Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.126063Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.126610Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d02/wp_woocommerce_shipping_zone_methods`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.127609Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d02/wp_woocommerce_shipping_zone_methods` because it could not be opened.
2025-06-10T12:22:13.128217Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.128585Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.128852Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.129206Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d02\wp_woocommerce_shipping_zones.ibd' OS error: 103
2025-06-10T12:22:13.129652Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.129892Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.130305Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d02/wp_woocommerce_shipping_zones`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.130945Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d02/wp_woocommerce_shipping_zones` because it could not be opened.
2025-06-10T12:22:13.131327Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.131686Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.131938Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.132293Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d02\wp_woocommerce_tax_rate_locations.ibd' OS error: 103
2025-06-10T12:22:13.132810Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.133053Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.133537Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d02/wp_woocommerce_tax_rate_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.134113Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d02/wp_woocommerce_tax_rate_locations` because it could not be opened.
2025-06-10T12:22:13.134594Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.134840Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.135090Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.135770Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d02\wp_woocommerce_tax_rates.ibd' OS error: 103
2025-06-10T12:22:13.136108Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.136403Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.136861Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d02/wp_woocommerce_tax_rates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.137492Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d02/wp_woocommerce_tax_rates` because it could not be opened.
2025-06-10T12:22:13.137976Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.138249Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.138567Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.139030Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_actionscheduler_actions.ibd' OS error: 103
2025-06-10T12:22:13.139433Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.139741Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.140124Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_actionscheduler_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.140958Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_actionscheduler_actions` because it could not be opened.
2025-06-10T12:22:13.141483Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.141759Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.142032Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.142503Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_actionscheduler_claims.ibd' OS error: 103
2025-06-10T12:22:13.142836Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.143118Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.143578Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_actionscheduler_claims`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.144130Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_actionscheduler_claims` because it could not be opened.
2025-06-10T12:22:13.144572Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.144823Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.145079Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.145583Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_actionscheduler_groups.ibd' OS error: 103
2025-06-10T12:22:13.145907Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.146148Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.146622Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_actionscheduler_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.147833Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_actionscheduler_groups` because it could not be opened.
2025-06-10T12:22:13.148409Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.149265Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.149539Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.150335Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_actionscheduler_logs.ibd' OS error: 103
2025-06-10T12:22:13.150843Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.151328Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.151923Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_actionscheduler_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.152624Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_actionscheduler_logs` because it could not be opened.
2025-06-10T12:22:13.153225Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.153538Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.153892Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.154378Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:13.154695Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.154950Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.155438Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.155975Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:13.156509Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.156774Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.157306Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.157784Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_comments.ibd' OS error: 103
2025-06-10T12:22:13.158182Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.158455Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.158895Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.159529Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_comments` because it could not be opened.
2025-06-10T12:22:13.160005Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.160346Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.160659Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.161034Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:13.161428Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.161721Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.162231Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.162852Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_fbv` because it could not be opened.
2025-06-10T12:22:13.163315Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.163573Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.163835Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.164310Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:13.164700Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.164962Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.165496Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.166133Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:13.166573Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.166832Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.167223Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.167602Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_kbp_countdown_entry.ibd' OS error: 103
2025-06-10T12:22:13.167945Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.168287Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.168695Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_kbp_countdown_entry`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.169336Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_kbp_countdown_entry` because it could not be opened.
2025-06-10T12:22:13.169737Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.170225Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.170682Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.171091Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_kbp_form_entry.ibd' OS error: 103
2025-06-10T12:22:13.171423Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.171730Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.172194Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_kbp_form_entry`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.172783Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_kbp_form_entry` because it could not be opened.
2025-06-10T12:22:13.173333Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.173613Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.173916Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.174331Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_kbp_form_entrymeta.ibd' OS error: 103
2025-06-10T12:22:13.174665Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.174977Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.175421Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_kbp_form_entrymeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.176067Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_kbp_form_entrymeta` because it could not be opened.
2025-06-10T12:22:13.176565Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.176895Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.177238Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.177607Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_links.ibd' OS error: 103
2025-06-10T12:22:13.177908Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.178219Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.178731Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.179372Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_links` because it could not be opened.
2025-06-10T12:22:13.179723Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.180080Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.180379Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.180877Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_options.ibd' OS error: 103
2025-06-10T12:22:13.181261Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.181524Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.182009Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.182824Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_options` because it could not be opened.
2025-06-10T12:22:13.183301Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.183834Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.184130Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.184535Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_post_views.ibd' OS error: 103
2025-06-10T12:22:13.184860Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.185110Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.185745Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_post_views`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.186385Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_post_views` because it could not be opened.
2025-06-10T12:22:13.186771Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.187036Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.187425Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.187795Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:13.188230Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.188518Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.188918Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.189544Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_postmeta` because it could not be opened.
2025-06-10T12:22:13.190045Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.190557Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.190863Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.191289Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_posts.ibd' OS error: 103
2025-06-10T12:22:13.191609Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.191873Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.192325Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.192901Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_posts` because it could not be opened.
2025-06-10T12:22:13.193318Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.193588Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.193860Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.194275Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:13.194617Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.194883Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.195333Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.195913Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:13.196355Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.196638Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.197189Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.197608Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:13.197945Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.198243Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.198670Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.199267Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:13.199693Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.199966Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.200270Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.200655Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:13.200971Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.201290Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.201826Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.202412Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_termmeta` because it could not be opened.
2025-06-10T12:22:13.202813Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.203084Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.203422Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.203840Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_terms.ibd' OS error: 103
2025-06-10T12:22:13.204243Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.205408Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.205942Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.206591Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_terms` because it could not be opened.
2025-06-10T12:22:13.206981Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.207373Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.207633Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.207994Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:13.208413Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.208676Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.209063Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.209686Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_usermeta` because it could not be opened.
2025-06-10T12:22:13.210051Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.210458Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.210716Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.211214Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_users.ibd' OS error: 103
2025-06-10T12:22:13.211516Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.211971Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.214005Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.214588Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_users` because it could not be opened.
2025-06-10T12:22:13.214953Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.215341Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.215610Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.216605Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_wc_admin_note_actions.ibd' OS error: 103
2025-06-10T12:22:13.217024Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.217388Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.217799Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_wc_admin_note_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.218466Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_wc_admin_note_actions` because it could not be opened.
2025-06-10T12:22:13.218890Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.219148Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.219551Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.220067Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_wc_admin_notes.ibd' OS error: 103
2025-06-10T12:22:13.220472Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.220803Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.221350Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_wc_admin_notes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.221935Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_wc_admin_notes` because it could not be opened.
2025-06-10T12:22:13.222473Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.222818Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.223099Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.223577Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_wc_category_lookup.ibd' OS error: 103
2025-06-10T12:22:13.223914Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.224329Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.224756Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_wc_category_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.225440Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_wc_category_lookup` because it could not be opened.
2025-06-10T12:22:13.225869Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.226123Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.226468Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.227044Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_wc_customer_lookup.ibd' OS error: 103
2025-06-10T12:22:13.227480Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.227743Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.228141Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_wc_customer_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.228761Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_wc_customer_lookup` because it could not be opened.
2025-06-10T12:22:13.229154Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.229522Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.229786Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.230151Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_wc_download_log.ibd' OS error: 103
2025-06-10T12:22:13.230580Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.230833Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.231303Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_wc_download_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.231859Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_wc_download_log` because it could not be opened.
2025-06-10T12:22:13.232279Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.232562Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.232822Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.233459Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_wc_order_coupon_lookup.ibd' OS error: 103
2025-06-10T12:22:13.233870Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.234122Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.234581Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_wc_order_coupon_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.235139Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_wc_order_coupon_lookup` because it could not be opened.
2025-06-10T12:22:13.235639Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.235892Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.236431Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.237140Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_wc_order_product_lookup.ibd' OS error: 103
2025-06-10T12:22:13.237676Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.237929Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.238504Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_wc_order_product_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.239080Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_wc_order_product_lookup` because it could not be opened.
2025-06-10T12:22:13.239557Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.239845Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.240112Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.240620Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_wc_order_stats.ibd' OS error: 103
2025-06-10T12:22:13.240971Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.241284Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.241800Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_wc_order_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.242589Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_wc_order_stats` because it could not be opened.
2025-06-10T12:22:13.243131Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.243892Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.244277Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.244732Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_wc_order_tax_lookup.ibd' OS error: 103
2025-06-10T12:22:13.246184Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.246498Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.247078Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_wc_order_tax_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.247796Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_wc_order_tax_lookup` because it could not be opened.
2025-06-10T12:22:13.248791Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.249135Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.249452Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.250109Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_wc_product_meta_lookup.ibd' OS error: 103
2025-06-10T12:22:13.250748Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.251118Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.251940Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_wc_product_meta_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.253131Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_wc_product_meta_lookup` because it could not be opened.
2025-06-10T12:22:13.254009Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.254605Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.254958Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.255337Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_wc_rate_limits.ibd' OS error: 103
2025-06-10T12:22:13.255777Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.256035Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.256427Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_wc_rate_limits`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.257065Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_wc_rate_limits` because it could not be opened.
2025-06-10T12:22:13.257617Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.257903Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.258159Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.258516Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_wc_reserved_stock.ibd' OS error: 103
2025-06-10T12:22:13.258937Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.259183Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.259609Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_wc_reserved_stock`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.260181Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_wc_reserved_stock` because it could not be opened.
2025-06-10T12:22:13.260562Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.260897Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.261234Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.261664Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_wc_tax_rate_classes.ibd' OS error: 103
2025-06-10T12:22:13.262232Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.262588Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.263016Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_wc_tax_rate_classes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.263661Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_wc_tax_rate_classes` because it could not be opened.
2025-06-10T12:22:13.264091Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.264364Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.264738Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.265139Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_wc_webhooks.ibd' OS error: 103
2025-06-10T12:22:13.265455Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.265833Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.266256Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_wc_webhooks`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.266964Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_wc_webhooks` because it could not be opened.
2025-06-10T12:22:13.267414Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.267789Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.268178Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.268610Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_woocommerce_api_keys.ibd' OS error: 103
2025-06-10T12:22:13.268990Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.269258Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.269753Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_woocommerce_api_keys`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.270323Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_woocommerce_api_keys` because it could not be opened.
2025-06-10T12:22:13.270815Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.271081Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.271349Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.271793Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_woocommerce_attribute_taxonomies.ibd' OS error: 103
2025-06-10T12:22:13.272155Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.272414Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.272882Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_woocommerce_attribute_taxonomies`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.273472Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_woocommerce_attribute_taxonomies` because it could not be opened.
2025-06-10T12:22:13.273957Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.274282Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.274617Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.275056Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_woocommerce_downloadable_product_permissions.ibd' OS error: 103
2025-06-10T12:22:13.275477Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.275784Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.276185Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_woocommerce_downloadable_product_permissions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.276852Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_woocommerce_downloadable_product_permissions` because it could not be opened.
2025-06-10T12:22:13.277296Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.277593Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.277934Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.278302Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_woocommerce_log.ibd' OS error: 103
2025-06-10T12:22:13.278703Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.278954Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.279344Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_woocommerce_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.280262Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_woocommerce_log` because it could not be opened.
2025-06-10T12:22:13.281117Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.281583Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.281992Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.282435Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_woocommerce_order_itemmeta.ibd' OS error: 103
2025-06-10T12:22:13.282776Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.283138Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.283574Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_woocommerce_order_itemmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.284517Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_woocommerce_order_itemmeta` because it could not be opened.
2025-06-10T12:22:13.285080Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.285364Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.285656Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.286059Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_woocommerce_order_items.ibd' OS error: 103
2025-06-10T12:22:13.286426Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.286693Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.287100Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_woocommerce_order_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.287803Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_woocommerce_order_items` because it could not be opened.
2025-06-10T12:22:13.288280Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.288568Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.288844Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.289335Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_woocommerce_payment_tokenmeta.ibd' OS error: 103
2025-06-10T12:22:13.289826Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.290082Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.290605Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_woocommerce_payment_tokenmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.291211Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_woocommerce_payment_tokenmeta` because it could not be opened.
2025-06-10T12:22:13.291842Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.292210Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.292538Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.292913Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_woocommerce_payment_tokens.ibd' OS error: 103
2025-06-10T12:22:13.293251Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.293651Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.294103Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_woocommerce_payment_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.294740Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_woocommerce_payment_tokens` because it could not be opened.
2025-06-10T12:22:13.295412Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.295799Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.296105Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.296525Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_woocommerce_sessions.ibd' OS error: 103
2025-06-10T12:22:13.296864Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.297125Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.297655Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_woocommerce_sessions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.298241Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_woocommerce_sessions` because it could not be opened.
2025-06-10T12:22:13.298679Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.298940Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.299205Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.299628Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_woocommerce_shipping_zone_locations.ibd' OS error: 103
2025-06-10T12:22:13.300004Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.300261Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.300683Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_woocommerce_shipping_zone_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.301478Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_woocommerce_shipping_zone_locations` because it could not be opened.
2025-06-10T12:22:13.301937Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.302192Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.302555Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.302912Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_woocommerce_shipping_zone_methods.ibd' OS error: 103
2025-06-10T12:22:13.303311Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.303681Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.304081Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_woocommerce_shipping_zone_methods`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.304737Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_woocommerce_shipping_zone_methods` because it could not be opened.
2025-06-10T12:22:13.305288Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.305688Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.305979Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.306479Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_woocommerce_shipping_zones.ibd' OS error: 103
2025-06-10T12:22:13.306832Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.307081Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.307828Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_woocommerce_shipping_zones`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.308473Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_woocommerce_shipping_zones` because it could not be opened.
2025-06-10T12:22:13.308899Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.309166Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.309470Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.309850Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_woocommerce_tax_rate_locations.ibd' OS error: 103
2025-06-10T12:22:13.310211Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.310546Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.311120Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_woocommerce_tax_rate_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.311874Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_woocommerce_tax_rate_locations` because it could not be opened.
2025-06-10T12:22:13.312286Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.312621Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.312874Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.313235Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_woocommerce_tax_rates.ibd' OS error: 103
2025-06-10T12:22:13.313698Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.313955Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.314372Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_woocommerce_tax_rates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.315034Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_woocommerce_tax_rates` because it could not be opened.
2025-06-10T12:22:13.315547Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.315816Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.316076Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.316524Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:13.316875Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.317149Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.317755Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.318377Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:13.318841Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.319093Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.319418Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.319960Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:13.320263Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.320655Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.321123Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.321783Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:13.322626Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.322889Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.323281Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.324764Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:13.325255Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.325582Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.326119Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.327093Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:13.327598Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.327866Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.328161Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.328560Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d03\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:13.328910Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.329175Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.329627Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d03/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.330220Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d03/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:13.330683Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.330951Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.331224Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.331657Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_actionscheduler_actions.ibd' OS error: 103
2025-06-10T12:22:13.332097Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.332444Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.332851Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_actionscheduler_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.333558Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_actionscheduler_actions` because it could not be opened.
2025-06-10T12:22:13.334013Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.334419Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.334719Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.335102Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_actionscheduler_claims.ibd' OS error: 103
2025-06-10T12:22:13.335541Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.335802Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.336215Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_actionscheduler_claims`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.336948Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_actionscheduler_claims` because it could not be opened.
2025-06-10T12:22:13.337456Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.337715Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.338037Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.338499Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_actionscheduler_groups.ibd' OS error: 103
2025-06-10T12:22:13.338857Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.339119Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.339562Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_actionscheduler_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.340147Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_actionscheduler_groups` because it could not be opened.
2025-06-10T12:22:13.340609Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.340884Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.341156Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.341610Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_actionscheduler_logs.ibd' OS error: 103
2025-06-10T12:22:13.341956Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.342228Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.342663Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_actionscheduler_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.343266Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_actionscheduler_logs` because it could not be opened.
2025-06-10T12:22:13.343695Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.343962Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.344251Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.344654Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:13.344974Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.345257Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.345678Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.346270Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:13.346662Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.346924Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.347193Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.347614Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_comments.ibd' OS error: 103
2025-06-10T12:22:13.347932Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.348233Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.348651Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.349361Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_comments` because it could not be opened.
2025-06-10T12:22:13.349761Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.350019Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.350351Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.350726Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:13.351015Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.351324Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.351756Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.352336Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_fbv` because it could not be opened.
2025-06-10T12:22:13.352675Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.352924Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.353176Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.354022Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:13.355932Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.357106Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.358549Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.359293Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:13.359740Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.360065Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.360377Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.360781Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_kbp_countdown_entry.ibd' OS error: 103
2025-06-10T12:22:13.361149Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.361469Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.361855Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_kbp_countdown_entry`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.362570Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_kbp_countdown_entry` because it could not be opened.
2025-06-10T12:22:13.363126Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.363548Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.363921Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.364350Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_kbp_form_entry.ibd' OS error: 103
2025-06-10T12:22:13.364696Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.365013Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.365521Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_kbp_form_entry`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.366135Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_kbp_form_entry` because it could not be opened.
2025-06-10T12:22:13.366623Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.366897Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.367185Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.367584Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_kbp_form_entrymeta.ibd' OS error: 103
2025-06-10T12:22:13.367922Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.368198Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.368629Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_kbp_form_entrymeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.369255Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_kbp_form_entrymeta` because it could not be opened.
2025-06-10T12:22:13.369666Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.369932Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.370219Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.370600Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_links.ibd' OS error: 103
2025-06-10T12:22:13.370910Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.371185Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.371651Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.372455Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_links` because it could not be opened.
2025-06-10T12:22:13.372830Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.373091Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.373473Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.373900Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_options.ibd' OS error: 103
2025-06-10T12:22:13.374325Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.374591Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.374984Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.375599Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_options` because it could not be opened.
2025-06-10T12:22:13.375976Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.376351Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.376625Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.376988Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_post_views.ibd' OS error: 103
2025-06-10T12:22:13.377382Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.377633Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.378025Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_post_views`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.378617Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_post_views` because it could not be opened.
2025-06-10T12:22:13.379002Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.379298Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.379584Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.379965Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:13.380298Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.380556Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.380969Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.381806Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_postmeta` because it could not be opened.
2025-06-10T12:22:13.382403Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.382685Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.382945Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.383368Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_posts.ibd' OS error: 103
2025-06-10T12:22:13.383663Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.383908Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.384369Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.384943Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_posts` because it could not be opened.
2025-06-10T12:22:13.385401Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.385649Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.385904Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.386331Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:13.386653Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.386949Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.388124Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.388781Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:13.389508Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.389770Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.390092Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.390528Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:13.390856Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.391924Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.392375Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.393018Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:13.393514Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.393892Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.394161Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.394530Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:13.394929Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.395181Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.395580Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.396330Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_termmeta` because it could not be opened.
2025-06-10T12:22:13.396925Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.397276Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.397724Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.398154Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_terms.ibd' OS error: 103
2025-06-10T12:22:13.398479Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.398803Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.399264Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.399877Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_terms` because it could not be opened.
2025-06-10T12:22:13.400271Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.400529Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.400860Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.401251Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:13.401556Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.401933Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.402328Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.402977Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_usermeta` because it could not be opened.
2025-06-10T12:22:13.403375Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.403648Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.404065Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.404546Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_users.ibd' OS error: 103
2025-06-10T12:22:13.405005Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.405282Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.405755Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.406428Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_users` because it could not be opened.
2025-06-10T12:22:13.406914Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.407215Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.407475Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.407969Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_wc_admin_note_actions.ibd' OS error: 103
2025-06-10T12:22:13.408301Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.408552Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.409006Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_wc_admin_note_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.409557Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_wc_admin_note_actions` because it could not be opened.
2025-06-10T12:22:13.410011Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.410259Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.410516Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.411017Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_wc_admin_notes.ibd' OS error: 103
2025-06-10T12:22:13.411323Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.411567Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.412063Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_wc_admin_notes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.412749Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_wc_admin_notes` because it could not be opened.
2025-06-10T12:22:13.413216Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.413469Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.413833Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.414204Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_wc_category_lookup.ibd' OS error: 103
2025-06-10T12:22:13.414592Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.414980Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.415372Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_wc_category_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.416052Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_wc_category_lookup` because it could not be opened.
2025-06-10T12:22:13.416526Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.416834Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.417105Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.417488Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_wc_customer_lookup.ibd' OS error: 103
2025-06-10T12:22:13.417854Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.418117Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.418568Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_wc_customer_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.419416Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_wc_customer_lookup` because it could not be opened.
2025-06-10T12:22:13.420715Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.421565Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.422140Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.422609Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_wc_download_log.ibd' OS error: 103
2025-06-10T12:22:13.423203Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.423475Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.423939Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_wc_download_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.424533Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_wc_download_log` because it could not be opened.
2025-06-10T12:22:13.424947Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.425225Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.425531Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.425911Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_wc_order_coupon_lookup.ibd' OS error: 103
2025-06-10T12:22:13.426296Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.426556Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.426972Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_wc_order_coupon_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.427593Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_wc_order_coupon_lookup` because it could not be opened.
2025-06-10T12:22:13.428029Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.428362Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.428823Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.429273Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_wc_order_product_lookup.ibd' OS error: 103
2025-06-10T12:22:13.429650Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.429906Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.430443Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_wc_order_product_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.431038Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_wc_order_product_lookup` because it could not be opened.
2025-06-10T12:22:13.431514Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.431762Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.432014Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.432465Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_wc_order_stats.ibd' OS error: 103
2025-06-10T12:22:13.432769Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.433009Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.433507Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_wc_order_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.434024Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_wc_order_stats` because it could not be opened.
2025-06-10T12:22:13.434564Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.434829Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.435251Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.435699Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_wc_order_tax_lookup.ibd' OS error: 103
2025-06-10T12:22:13.436040Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.436369Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.436839Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_wc_order_tax_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.437650Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_wc_order_tax_lookup` because it could not be opened.
2025-06-10T12:22:13.438060Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.438396Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.438656Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.439020Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_wc_product_meta_lookup.ibd' OS error: 103
2025-06-10T12:22:13.439510Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.439756Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.440162Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_wc_product_meta_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.440751Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_wc_product_meta_lookup` because it could not be opened.
2025-06-10T12:22:13.441125Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.441631Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.441916Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.442406Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_wc_rate_limits.ibd' OS error: 103
2025-06-10T12:22:13.442725Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.442975Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.443459Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_wc_rate_limits`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.443996Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_wc_rate_limits` because it could not be opened.
2025-06-10T12:22:13.444453Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.444712Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.444972Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.445457Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_wc_reserved_stock.ibd' OS error: 103
2025-06-10T12:22:13.445792Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.446171Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.446603Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_wc_reserved_stock`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.447179Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_wc_reserved_stock` because it could not be opened.
2025-06-10T12:22:13.447731Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.447984Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.448333Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.448711Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_wc_tax_rate_classes.ibd' OS error: 103
2025-06-10T12:22:13.449151Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.449427Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.449810Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_wc_tax_rate_classes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.450549Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_wc_tax_rate_classes` because it could not be opened.
2025-06-10T12:22:13.451108Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.451663Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.452378Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.453702Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_wc_webhooks.ibd' OS error: 103
2025-06-10T12:22:13.454755Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.455026Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.455525Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_wc_webhooks`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.456125Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_wc_webhooks` because it could not be opened.
2025-06-10T12:22:13.456584Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.456850Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.457209Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.457625Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_woocommerce_api_keys.ibd' OS error: 103
2025-06-10T12:22:13.457968Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.458254Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.458766Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_woocommerce_api_keys`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.459502Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_woocommerce_api_keys` because it could not be opened.
2025-06-10T12:22:13.459956Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.460214Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.460657Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.461105Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_woocommerce_attribute_taxonomies.ibd' OS error: 103
2025-06-10T12:22:13.461692Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.461964Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.462508Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_woocommerce_attribute_taxonomies`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.463110Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_woocommerce_attribute_taxonomies` because it could not be opened.
2025-06-10T12:22:13.463738Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.463998Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.464319Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.464703Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_woocommerce_downloadable_product_permissions.ibd' OS error: 103
2025-06-10T12:22:13.465081Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.465431Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.465871Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_woocommerce_downloadable_product_permissions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.466664Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_woocommerce_downloadable_product_permissions` because it could not be opened.
2025-06-10T12:22:13.467157Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.467495Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.467774Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.468141Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_woocommerce_log.ibd' OS error: 103
2025-06-10T12:22:13.468528Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.468779Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.469174Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_woocommerce_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.469806Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_woocommerce_log` because it could not be opened.
2025-06-10T12:22:13.470197Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.470543Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.470908Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.471370Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_woocommerce_order_itemmeta.ibd' OS error: 103
2025-06-10T12:22:13.471729Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.471983Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.472478Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_woocommerce_order_itemmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.473039Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_woocommerce_order_itemmeta` because it could not be opened.
2025-06-10T12:22:13.473664Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.473936Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.474252Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.474735Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_woocommerce_order_items.ibd' OS error: 103
2025-06-10T12:22:13.475099Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.475420Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.475817Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_woocommerce_order_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.476451Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_woocommerce_order_items` because it could not be opened.
2025-06-10T12:22:13.476966Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.477335Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.477633Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.478020Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_woocommerce_payment_tokenmeta.ibd' OS error: 103
2025-06-10T12:22:13.478453Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.478713Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.479117Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_woocommerce_payment_tokenmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.479759Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_woocommerce_payment_tokenmeta` because it could not be opened.
2025-06-10T12:22:13.480205Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.480571Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.480832Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.481247Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_woocommerce_payment_tokens.ibd' OS error: 103
2025-06-10T12:22:13.481621Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.481874Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.483048Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_woocommerce_payment_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.483883Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_woocommerce_payment_tokens` because it could not be opened.
2025-06-10T12:22:13.485430Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.485957Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.486376Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.487073Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_woocommerce_sessions.ibd' OS error: 103
2025-06-10T12:22:13.487438Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.487702Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.488112Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_woocommerce_sessions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.488731Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_woocommerce_sessions` because it could not be opened.
2025-06-10T12:22:13.489188Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.489460Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.489725Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.490106Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_woocommerce_shipping_zone_locations.ibd' OS error: 103
2025-06-10T12:22:13.490513Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.490774Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.491214Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_woocommerce_shipping_zone_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.491867Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_woocommerce_shipping_zone_locations` because it could not be opened.
2025-06-10T12:22:13.492410Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.492716Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.493030Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.493597Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_woocommerce_shipping_zone_methods.ibd' OS error: 103
2025-06-10T12:22:13.493997Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.494365Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.494778Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_woocommerce_shipping_zone_methods`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.495505Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_woocommerce_shipping_zone_methods` because it could not be opened.
2025-06-10T12:22:13.495952Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.496293Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.496621Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.496997Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_woocommerce_shipping_zones.ibd' OS error: 103
2025-06-10T12:22:13.497394Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.497645Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.498046Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_woocommerce_shipping_zones`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.498790Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_woocommerce_shipping_zones` because it could not be opened.
2025-06-10T12:22:13.499262Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.499578Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.499868Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.500383Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_woocommerce_tax_rate_locations.ibd' OS error: 103
2025-06-10T12:22:13.500787Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.501043Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.501517Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_woocommerce_tax_rate_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.502088Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_woocommerce_tax_rate_locations` because it could not be opened.
2025-06-10T12:22:13.502599Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.502855Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.503116Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.503579Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_woocommerce_tax_rates.ibd' OS error: 103
2025-06-10T12:22:13.503914Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.504394Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.504821Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_woocommerce_tax_rates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.505421Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_woocommerce_tax_rates` because it could not be opened.
2025-06-10T12:22:13.505799Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.506102Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.506472Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.506923Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:13.507318Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.507583Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.508002Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.508739Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:13.509391Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.509701Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.509984Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.510449Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:13.510776Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.511038Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.511499Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.512068Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:13.512524Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.512907Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.513309Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.513698Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:13.514068Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.514390Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.514786Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.515647Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:13.516293Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.516566Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.516877Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.517301Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d04\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:13.517651Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.517911Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.518364Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d04/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.518946Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d04/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:13.519607Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.519933Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.520298Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.520728Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_actionscheduler_actions.ibd' OS error: 103
2025-06-10T12:22:13.521104Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.521368Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.521800Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_actionscheduler_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.522412Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_actionscheduler_actions` because it could not be opened.
2025-06-10T12:22:13.522851Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.523143Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.523415Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.523805Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_actionscheduler_claims.ibd' OS error: 103
2025-06-10T12:22:13.524188Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.524452Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.524877Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_actionscheduler_claims`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.525531Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_actionscheduler_claims` because it could not be opened.
2025-06-10T12:22:13.526189Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.526467Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.526730Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.527206Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_actionscheduler_groups.ibd' OS error: 103
2025-06-10T12:22:13.527550Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.527882Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.528346Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_actionscheduler_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.528894Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_actionscheduler_groups` because it could not be opened.
2025-06-10T12:22:13.529438Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.529854Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.530314Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.530741Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_actionscheduler_logs.ibd' OS error: 103
2025-06-10T12:22:13.531154Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.531406Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.531797Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_actionscheduler_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.532477Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_actionscheduler_logs` because it could not be opened.
2025-06-10T12:22:13.532958Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.533369Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.533622Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.534067Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_aioseo_notifications.ibd' OS error: 103
2025-06-10T12:22:13.534403Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.534646Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.535138Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_aioseo_notifications`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.535679Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_aioseo_notifications` because it could not be opened.
2025-06-10T12:22:13.536142Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.536388Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.536638Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.537075Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_aioseo_posts.ibd' OS error: 103
2025-06-10T12:22:13.537381Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.537622Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.538171Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_aioseo_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.538751Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_aioseo_posts` because it could not be opened.
2025-06-10T12:22:13.539215Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.539463Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.539760Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.540267Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:13.540578Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.540824Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.541410Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.542005Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:13.542402Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.542657Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.542965Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.543477Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_comments.ibd' OS error: 103
2025-06-10T12:22:13.543813Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.544114Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.544502Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.545150Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_comments` because it could not be opened.
2025-06-10T12:22:13.545540Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.545787Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.546161Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.546515Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:13.546809Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.547140Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.547516Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.548119Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_fbv` because it could not be opened.
2025-06-10T12:22:13.548445Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.548686Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.549016Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.549395Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:13.549712Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.550042Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.550438Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.551071Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:13.551423Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.551683Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.551994Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.552537Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_kbp_countdown_entry.ibd' OS error: 103
2025-06-10T12:22:13.552920Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.553269Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.553705Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_kbp_countdown_entry`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.554333Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_kbp_countdown_entry` because it could not be opened.
2025-06-10T12:22:13.554763Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.555062Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.555329Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.555710Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_kbp_form_entry.ibd' OS error: 103
2025-06-10T12:22:13.556080Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.556340Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.556756Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_kbp_form_entry`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.557396Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_kbp_form_entry` because it could not be opened.
2025-06-10T12:22:13.557885Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.558180Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.558448Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.558854Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_kbp_form_entrymeta.ibd' OS error: 103
2025-06-10T12:22:13.559254Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.559503Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.559954Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_kbp_form_entrymeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.560518Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_kbp_form_entrymeta` because it could not be opened.
2025-06-10T12:22:13.560955Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.561215Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.561469Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.561860Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_links.ibd' OS error: 103
2025-06-10T12:22:13.562196Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.562446Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.562984Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.564244Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_links` because it could not be opened.
2025-06-10T12:22:13.564647Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.565390Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.566160Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.567070Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_options.ibd' OS error: 103
2025-06-10T12:22:13.567559Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.568025Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.568472Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.569021Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_options` because it could not be opened.
2025-06-10T12:22:13.569466Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.569734Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.570004Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.570444Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:13.570766Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.571032Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.571520Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.572080Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_postmeta` because it could not be opened.
2025-06-10T12:22:13.572560Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.572835Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.573110Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.573521Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_posts.ibd' OS error: 103
2025-06-10T12:22:13.573842Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.574104Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.574573Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.575335Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_posts` because it could not be opened.
2025-06-10T12:22:13.575823Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.576157Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.576521Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.576887Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:13.577289Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.577599Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.577994Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.578610Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:13.579065Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.579431Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.579697Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.580065Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:13.580426Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.580677Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.581066Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.581694Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:13.582058Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.582376Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.582644Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.583005Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:13.583462Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.583757Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.584168Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.584764Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_termmeta` because it could not be opened.
2025-06-10T12:22:13.585218Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.585537Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.585799Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.586241Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_terms.ibd' OS error: 103
2025-06-10T12:22:13.586582Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.586851Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.587320Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.587853Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_terms` because it could not be opened.
2025-06-10T12:22:13.588544Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.588822Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.589110Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.589621Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:13.589983Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.590287Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.590711Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.591366Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_usermeta` because it could not be opened.
2025-06-10T12:22:13.591776Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.592046Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.592353Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.592761Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_users.ibd' OS error: 103
2025-06-10T12:22:13.593059Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.593358Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.593752Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.594346Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_users` because it could not be opened.
2025-06-10T12:22:13.594771Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.595043Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.595766Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.596559Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_wc_admin_note_actions.ibd' OS error: 103
2025-06-10T12:22:13.597184Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.598177Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.598785Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_wc_admin_note_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.599818Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_wc_admin_note_actions` because it could not be opened.
2025-06-10T12:22:13.600447Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.600732Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.601197Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.601744Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_wc_admin_notes.ibd' OS error: 103
2025-06-10T12:22:13.602084Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.602370Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.602811Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_wc_admin_notes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.603400Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_wc_admin_notes` because it could not be opened.
2025-06-10T12:22:13.603902Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.604165Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.604543Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.605006Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_wc_category_lookup.ibd' OS error: 103
2025-06-10T12:22:13.605446Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.605751Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.606180Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_wc_category_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.606808Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_wc_category_lookup` because it could not be opened.
2025-06-10T12:22:13.607358Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.607703Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.608154Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.608640Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_wc_customer_lookup.ibd' OS error: 103
2025-06-10T12:22:13.609029Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.609282Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.609826Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_wc_customer_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.610497Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_wc_customer_lookup` because it could not be opened.
2025-06-10T12:22:13.610908Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.611165Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.611497Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.611860Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_wc_download_log.ibd' OS error: 103
2025-06-10T12:22:13.612175Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.612524Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.612912Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_wc_download_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.613598Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_wc_download_log` because it could not be opened.
2025-06-10T12:22:13.613964Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.614265Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.614640Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.615009Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_wc_order_coupon_lookup.ibd' OS error: 103
2025-06-10T12:22:13.615383Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.615646Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.616034Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_wc_order_coupon_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.616686Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_wc_order_coupon_lookup` because it could not be opened.
2025-06-10T12:22:13.617090Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.617386Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.617682Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.618054Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_wc_order_product_lookup.ibd' OS error: 103
2025-06-10T12:22:13.618437Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.618696Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.619102Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_wc_order_product_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.619713Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_wc_order_product_lookup` because it could not be opened.
2025-06-10T12:22:13.620128Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.620435Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.620811Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.621232Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_wc_order_stats.ibd' OS error: 103
2025-06-10T12:22:13.621615Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.621880Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.622318Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_wc_order_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.622904Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_wc_order_stats` because it could not be opened.
2025-06-10T12:22:13.623348Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.623660Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.623925Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.624350Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_wc_order_tax_lookup.ibd' OS error: 103
2025-06-10T12:22:13.624762Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.625009Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.625517Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_wc_order_tax_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.626795Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_wc_order_tax_lookup` because it could not be opened.
2025-06-10T12:22:13.627853Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.628129Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.628934Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.629422Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_wc_product_meta_lookup.ibd' OS error: 103
2025-06-10T12:22:13.630919Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.631190Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.631652Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_wc_product_meta_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.632232Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_wc_product_meta_lookup` because it could not be opened.
2025-06-10T12:22:13.632700Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.632964Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.633231Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.633658Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_wc_rate_limits.ibd' OS error: 103
2025-06-10T12:22:13.633997Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.634260Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.634846Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_wc_rate_limits`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.635600Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_wc_rate_limits` because it could not be opened.
2025-06-10T12:22:13.636073Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.636387Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.636662Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.637040Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_wc_reserved_stock.ibd' OS error: 103
2025-06-10T12:22:13.637432Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.637698Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.638160Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_wc_reserved_stock`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.638823Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_wc_reserved_stock` because it could not be opened.
2025-06-10T12:22:13.639269Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.639564Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.639838Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.640221Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_wc_tax_rate_classes.ibd' OS error: 103
2025-06-10T12:22:13.640593Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.640856Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.641283Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_wc_tax_rate_classes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.641910Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_wc_tax_rate_classes` because it could not be opened.
2025-06-10T12:22:13.642348Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.642683Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.642998Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.643476Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_wc_webhooks.ibd' OS error: 103
2025-06-10T12:22:13.643798Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.644060Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.644510Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_wc_webhooks`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.645063Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_wc_webhooks` because it could not be opened.
2025-06-10T12:22:13.645492Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.645760Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.646029Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.646444Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_woocommerce_api_keys.ibd' OS error: 103
2025-06-10T12:22:13.646784Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.647041Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.647525Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_woocommerce_api_keys`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.648100Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_woocommerce_api_keys` because it could not be opened.
2025-06-10T12:22:13.648529Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.648792Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.649059Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.649501Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_woocommerce_attribute_taxonomies.ibd' OS error: 103
2025-06-10T12:22:13.649869Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.650128Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.650579Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_woocommerce_attribute_taxonomies`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.651172Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_woocommerce_attribute_taxonomies` because it could not be opened.
2025-06-10T12:22:13.651638Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.651903Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.652175Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.652603Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_woocommerce_downloadable_product_permissions.ibd' OS error: 103
2025-06-10T12:22:13.653149Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.653460Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.653869Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_woocommerce_downloadable_product_permissions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.654540Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_woocommerce_downloadable_product_permissions` because it could not be opened.
2025-06-10T12:22:13.655012Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.655328Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.655599Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.655974Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_woocommerce_log.ibd' OS error: 103
2025-06-10T12:22:13.656351Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.656608Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.657012Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_woocommerce_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.657762Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_woocommerce_log` because it could not be opened.
2025-06-10T12:22:13.659983Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.661322Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.661997Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.662458Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_woocommerce_order_itemmeta.ibd' OS error: 103
2025-06-10T12:22:13.662850Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.663117Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.663582Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_woocommerce_order_itemmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.664408Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_woocommerce_order_itemmeta` because it could not be opened.
2025-06-10T12:22:13.664931Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.665208Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.665481Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.665926Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_woocommerce_order_items.ibd' OS error: 103
2025-06-10T12:22:13.666359Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.666609Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.667082Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_woocommerce_order_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.667674Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_woocommerce_order_items` because it could not be opened.
2025-06-10T12:22:13.668213Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.668483Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.668759Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.669277Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_woocommerce_payment_tokenmeta.ibd' OS error: 103
2025-06-10T12:22:13.669821Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.670137Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.670566Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_woocommerce_payment_tokenmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.671214Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_woocommerce_payment_tokenmeta` because it could not be opened.
2025-06-10T12:22:13.671666Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.671961Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.672228Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.672605Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_woocommerce_payment_tokens.ibd' OS error: 103
2025-06-10T12:22:13.673003Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.673263Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.673670Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_woocommerce_payment_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.674288Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_woocommerce_payment_tokens` because it could not be opened.
2025-06-10T12:22:13.674694Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.674984Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.675252Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.675631Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_woocommerce_sessions.ibd' OS error: 103
2025-06-10T12:22:13.676062Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.676366Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.676797Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_woocommerce_sessions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.677395Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_woocommerce_sessions` because it could not be opened.
2025-06-10T12:22:13.677825Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.678091Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.678359Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.678738Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_woocommerce_shipping_zone_locations.ibd' OS error: 103
2025-06-10T12:22:13.679149Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.679409Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.679861Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_woocommerce_shipping_zone_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.680478Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_woocommerce_shipping_zone_locations` because it could not be opened.
2025-06-10T12:22:13.680938Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.681204Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.681471Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.681884Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_woocommerce_shipping_zone_methods.ibd' OS error: 103
2025-06-10T12:22:13.682255Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.682678Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.683149Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_woocommerce_shipping_zone_methods`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.683729Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_woocommerce_shipping_zone_methods` because it could not be opened.
2025-06-10T12:22:13.684271Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.684530Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.684887Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.685298Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_woocommerce_shipping_zones.ibd' OS error: 103
2025-06-10T12:22:13.685653Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.685973Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.686417Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_woocommerce_shipping_zones`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.687041Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_woocommerce_shipping_zones` because it could not be opened.
2025-06-10T12:22:13.687451Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.687703Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.688053Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.688417Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_woocommerce_tax_rate_locations.ibd' OS error: 103
2025-06-10T12:22:13.688804Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.689075Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.689461Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_woocommerce_tax_rate_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.690116Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_woocommerce_tax_rate_locations` because it could not be opened.
2025-06-10T12:22:13.690591Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.690966Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.691284Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.691732Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_woocommerce_tax_rates.ibd' OS error: 103
2025-06-10T12:22:13.692689Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.693442Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.694613Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_woocommerce_tax_rates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.695275Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_woocommerce_tax_rates` because it could not be opened.
2025-06-10T12:22:13.695784Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.696055Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.696340Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.696737Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:13.697079Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.697357Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.697869Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.698610Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:13.699115Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.699512Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.699853Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.700698Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:13.701026Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.701356Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.701781Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.702431Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:13.702870Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.703160Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.703465Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.703858Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:13.704222Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.704490Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.704924Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.705515Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:13.705894Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.706193Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.706470Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.706862Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:13.707246Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.707511Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.707924Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.708543Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:13.708941Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.709233Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.709506Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.709887Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d05\wp_ywcdd_calendar.ibd' OS error: 103
2025-06-10T12:22:13.710294Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.710606Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.711074Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d05/wp_ywcdd_calendar`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.711685Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d05/wp_ywcdd_calendar` because it could not be opened.
2025-06-10T12:22:13.712114Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.712436Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.712709Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.713107Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d06\wp_actionscheduler_actions.ibd' OS error: 103
2025-06-10T12:22:13.713467Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.713731Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.714176Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d06/wp_actionscheduler_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.714783Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d06/wp_actionscheduler_actions` because it could not be opened.
2025-06-10T12:22:13.715209Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.715477Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.715749Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.716161Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d06\wp_actionscheduler_claims.ibd' OS error: 103
2025-06-10T12:22:13.716514Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.716783Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.717400Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d06/wp_actionscheduler_claims`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.718289Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d06/wp_actionscheduler_claims` because it could not be opened.
2025-06-10T12:22:13.718742Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.719011Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.719321Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.719702Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d06\wp_actionscheduler_groups.ibd' OS error: 103
2025-06-10T12:22:13.720054Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.720349Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.720760Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d06/wp_actionscheduler_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.721421Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d06/wp_actionscheduler_groups` because it could not be opened.
2025-06-10T12:22:13.721821Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.722103Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.722394Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.722790Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d06\wp_actionscheduler_logs.ibd' OS error: 103
2025-06-10T12:22:13.724933Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.725213Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.725724Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d06/wp_actionscheduler_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.727011Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d06/wp_actionscheduler_logs` because it could not be opened.
2025-06-10T12:22:13.727553Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.727833Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.728130Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.728560Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d06\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:13.728885Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.729146Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.729630Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d06/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.730195Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d06/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:13.730632Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.730895Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.731167Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.731607Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d06\wp_comments.ibd' OS error: 103
2025-06-10T12:22:13.731982Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.732262Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.732755Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d06/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.733355Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d06/wp_comments` because it could not be opened.
2025-06-10T12:22:13.733845Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.734130Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.734450Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.734844Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d06\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:13.735161Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.735468Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.735893Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d06/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.736481Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d06/wp_fbv` because it could not be opened.
2025-06-10T12:22:13.736869Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.737142Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.737448Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.737945Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d06\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:13.738352Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.738654Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.739073Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d06/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.739685Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d06/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:13.740114Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.740430Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.740835Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.741431Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d06\wp_kbp_countdown_entry.ibd' OS error: 103
2025-06-10T12:22:13.741932Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.742249Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.742689Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d06/wp_kbp_countdown_entry`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.743263Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d06/wp_kbp_countdown_entry` because it could not be opened.
2025-06-10T12:22:13.743704Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.743967Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.744390Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.744808Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d06\wp_kbp_form_entry.ibd' OS error: 103
2025-06-10T12:22:13.745146Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.745441Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.745858Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d06/wp_kbp_form_entry`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.746467Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d06/wp_kbp_form_entry` because it could not be opened.
2025-06-10T12:22:13.746880Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.747143Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.747457Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.747843Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d06\wp_kbp_form_entrymeta.ibd' OS error: 103
2025-06-10T12:22:13.748183Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.748498Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.748913Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d06/wp_kbp_form_entrymeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.749517Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d06/wp_kbp_form_entrymeta` because it could not be opened.
2025-06-10T12:22:13.749924Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.750185Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.750485Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.750869Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d06\wp_links.ibd' OS error: 103
2025-06-10T12:22:13.751162Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.751501Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.751893Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d06/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.752468Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d06/wp_links` because it could not be opened.
2025-06-10T12:22:13.752809Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.753060Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.753350Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.753803Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d06\wp_options.ibd' OS error: 103
2025-06-10T12:22:13.755153Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.755533Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.756252Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d06/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.758221Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d06/wp_options` because it could not be opened.
2025-06-10T12:22:13.759208Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.759519Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.760012Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.760455Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d06\wp_post_views.ibd' OS error: 103
2025-06-10T12:22:13.760859Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.761202Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.761660Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d06/wp_post_views`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.762336Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d06/wp_post_views` because it could not be opened.
2025-06-10T12:22:13.762741Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.763073Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.763336Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.763707Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d06\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:13.764236Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.764636Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.765211Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d06/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.765768Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d06/wp_postmeta` because it could not be opened.
2025-06-10T12:22:13.766307Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.766648Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.766957Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.767520Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d06\wp_posts.ibd' OS error: 103
2025-06-10T12:22:13.767900Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.768381Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.768861Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d06/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.769410Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d06/wp_posts` because it could not be opened.
2025-06-10T12:22:13.769837Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.770113Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.770423Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.770822Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d06\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:13.771188Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.771441Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.772012Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d06/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.772589Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d06/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:13.773154Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.773410Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.773668Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.774149Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d06\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:13.774696Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.775097Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.775632Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d06/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.776282Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d06/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:13.776689Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.777021Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.777292Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.777673Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d06\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:13.778107Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.778418Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.778906Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d06/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.779470Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d06/wp_termmeta` because it could not be opened.
2025-06-10T12:22:13.779947Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.780230Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.780502Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.780937Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d06\wp_terms.ibd' OS error: 103
2025-06-10T12:22:13.781296Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.781570Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.781998Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d06/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.782556Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d06/wp_terms` because it could not be opened.
2025-06-10T12:22:13.783005Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.783271Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.783540Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.783989Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d06\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:13.784307Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.784568Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.785035Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d06/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.785587Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d06/wp_usermeta` because it could not be opened.
2025-06-10T12:22:13.786017Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.786284Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.786554Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.787013Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d06\wp_users.ibd' OS error: 103
2025-06-10T12:22:13.787360Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.787632Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.788154Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d06/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.788749Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d06/wp_users` because it could not be opened.
2025-06-10T12:22:13.789170Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.789442Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.789728Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.790196Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d06\wp_wc_admin_note_actions.ibd' OS error: 103
2025-06-10T12:22:13.790550Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.790880Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.791290Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d06/wp_wc_admin_note_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.791963Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d06/wp_wc_admin_note_actions` because it could not be opened.
2025-06-10T12:22:13.792377Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.792638Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.792958Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.793343Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d06\wp_wc_admin_notes.ibd' OS error: 103
2025-06-10T12:22:13.793719Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.794005Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.794413Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d06/wp_wc_admin_notes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.795174Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d06/wp_wc_admin_notes` because it could not be opened.
2025-06-10T12:22:13.795684Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.796008Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.796284Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.796674Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d06\wp_wc_category_lookup.ibd' OS error: 103
2025-06-10T12:22:13.797098Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.797362Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.797868Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d06/wp_wc_category_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.798476Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d06/wp_wc_category_lookup` because it could not be opened.
2025-06-10T12:22:13.799001Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.799253Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.799510Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.799959Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d06\wp_wc_customer_lookup.ibd' OS error: 103
2025-06-10T12:22:13.800457Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.800840Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.801234Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d06/wp_wc_customer_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.801861Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d06/wp_wc_customer_lookup` because it could not be opened.
2025-06-10T12:22:13.802529Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.803351Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.804631Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.806232Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d06\wp_wc_download_log.ibd' OS error: 103
2025-06-10T12:22:13.806616Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.807421Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.807961Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d06/wp_wc_download_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.808607Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d06/wp_wc_download_log` because it could not be opened.
2025-06-10T12:22:13.809096Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.809568Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.809897Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.810344Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d06\wp_wc_order_coupon_lookup.ibd' OS error: 103
2025-06-10T12:22:13.810739Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.811139Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.811542Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d06/wp_wc_order_coupon_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.812241Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d06/wp_wc_order_coupon_lookup` because it could not be opened.
2025-06-10T12:22:13.812820Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.813138Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.813416Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.813889Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d06\wp_wc_order_product_lookup.ibd' OS error: 103
2025-06-10T12:22:13.814228Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.814482Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.814991Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d06/wp_wc_order_product_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.815592Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d06/wp_wc_order_product_lookup` because it could not be opened.
2025-06-10T12:22:13.816092Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.816365Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.816720Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.817119Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d06\wp_wc_order_stats.ibd' OS error: 103
2025-06-10T12:22:13.817445Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.817765Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.818210Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d06/wp_wc_order_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.818914Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d06/wp_wc_order_stats` because it could not be opened.
2025-06-10T12:22:13.819314Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.819578Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.819982Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.820351Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d06\wp_wc_order_tax_lookup.ibd' OS error: 103
2025-06-10T12:22:13.820794Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.821060Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.821452Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d06/wp_wc_order_tax_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.822122Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d06/wp_wc_order_tax_lookup` because it could not be opened.
2025-06-10T12:22:13.822592Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.822975Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.823269Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.823667Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d06\wp_wc_product_meta_lookup.ibd' OS error: 103
2025-06-10T12:22:13.824035Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.824287Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.824759Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d06/wp_wc_product_meta_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.825330Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d06/wp_wc_product_meta_lookup` because it could not be opened.
2025-06-10T12:22:13.825802Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.826105Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.826425Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.826864Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d06\wp_wc_rate_limits.ibd' OS error: 103
2025-06-10T12:22:13.827202Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.827464Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.827903Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d06/wp_wc_rate_limits`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.828475Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d06/wp_wc_rate_limits` because it could not be opened.
2025-06-10T12:22:13.828995Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.829280Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.829551Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.829961Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d06\wp_wc_reserved_stock.ibd' OS error: 103
2025-06-10T12:22:13.830292Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.830555Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.830993Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d06/wp_wc_reserved_stock`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.831562Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d06/wp_wc_reserved_stock` because it could not be opened.
2025-06-10T12:22:13.831994Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.832254Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.832525Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.833098Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d06\wp_wc_tax_rate_classes.ibd' OS error: 103
2025-06-10T12:22:13.833441Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.833732Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.834141Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d06/wp_wc_tax_rate_classes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.834747Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d06/wp_wc_tax_rate_classes` because it could not be opened.
2025-06-10T12:22:13.835371Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.835633Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.835936Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.836385Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d06\wp_wc_webhooks.ibd' OS error: 103
2025-06-10T12:22:13.836704Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.837356Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.837769Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d06/wp_wc_webhooks`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.838476Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d06/wp_wc_webhooks` because it could not be opened.
2025-06-10T12:22:13.839296Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.839580Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.839858Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.840281Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d06\wp_woocommerce_api_keys.ibd' OS error: 103
2025-06-10T12:22:13.840642Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.840900Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.841346Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d06/wp_woocommerce_api_keys`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.841927Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d06/wp_woocommerce_api_keys` because it could not be opened.
2025-06-10T12:22:13.842501Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.842920Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.843312Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.843691Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d06\wp_woocommerce_attribute_taxonomies.ibd' OS error: 103
2025-06-10T12:22:13.844101Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.844390Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.844795Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d06/wp_woocommerce_attribute_taxonomies`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.845567Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d06/wp_woocommerce_attribute_taxonomies` because it could not be opened.
2025-06-10T12:22:13.846238Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.846521Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.846880Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.847294Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d06\wp_woocommerce_downloadable_product_permissions.ibd' OS error: 103
2025-06-10T12:22:13.847728Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.848034Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.848496Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d06/wp_woocommerce_downloadable_product_permissions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.849941Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d06/wp_woocommerce_downloadable_product_permissions` because it could not be opened.
2025-06-10T12:22:13.850563Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.850924Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.851465Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.851826Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d06\wp_woocommerce_log.ibd' OS error: 103
2025-06-10T12:22:13.852321Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.852570Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.852951Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d06/wp_woocommerce_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.853852Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d06/wp_woocommerce_log` because it could not be opened.
2025-06-10T12:22:13.854434Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.854751Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.855096Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.855481Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d06\wp_woocommerce_order_itemmeta.ibd' OS error: 103
2025-06-10T12:22:13.855895Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.856248Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.856632Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d06/wp_woocommerce_order_itemmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.857403Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d06/wp_woocommerce_order_itemmeta` because it could not be opened.
2025-06-10T12:22:13.857887Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.858198Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.858465Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.858848Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d06\wp_woocommerce_order_items.ibd' OS error: 103
2025-06-10T12:22:13.859259Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.859522Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.859936Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d06/wp_woocommerce_order_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.860612Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d06/wp_woocommerce_order_items` because it could not be opened.
2025-06-10T12:22:13.861096Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.861422Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.861688Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.862136Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d06\wp_woocommerce_payment_tokenmeta.ibd' OS error: 103
2025-06-10T12:22:13.862498Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.862761Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.863237Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d06/wp_woocommerce_payment_tokenmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.863834Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d06/wp_woocommerce_payment_tokenmeta` because it could not be opened.
2025-06-10T12:22:13.864326Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.864571Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.864823Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.865313Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d06\wp_woocommerce_payment_tokens.ibd' OS error: 103
2025-06-10T12:22:13.865652Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.866352Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.867573Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d06/wp_woocommerce_payment_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.870048Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d06/wp_woocommerce_payment_tokens` because it could not be opened.
2025-06-10T12:22:13.870568Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.870839Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.871133Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.871580Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d06\wp_woocommerce_sessions.ibd' OS error: 103
2025-06-10T12:22:13.871944Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.872225Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.872660Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d06/wp_woocommerce_sessions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.873332Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d06/wp_woocommerce_sessions` because it could not be opened.
2025-06-10T12:22:13.873771Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.874140Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.874415Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.874800Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d06\wp_woocommerce_shipping_zone_locations.ibd' OS error: 103
2025-06-10T12:22:13.875257Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.875520Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.875936Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d06/wp_woocommerce_shipping_zone_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.876640Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d06/wp_woocommerce_shipping_zone_locations` because it could not be opened.
2025-06-10T12:22:13.877200Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.877484Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.877758Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.878220Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d06\wp_woocommerce_shipping_zone_methods.ibd' OS error: 103
2025-06-10T12:22:13.878745Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.879047Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.879448Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d06/wp_woocommerce_shipping_zone_methods`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.880096Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d06/wp_woocommerce_shipping_zone_methods` because it could not be opened.
2025-06-10T12:22:13.880590Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.880847Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.881172Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.881543Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d06\wp_woocommerce_shipping_zones.ibd' OS error: 103
2025-06-10T12:22:13.881919Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.882228Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.882623Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d06/wp_woocommerce_shipping_zones`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.883303Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d06/wp_woocommerce_shipping_zones` because it could not be opened.
2025-06-10T12:22:13.883716Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.883999Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.884274Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.884819Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d06\wp_woocommerce_tax_rate_locations.ibd' OS error: 103
2025-06-10T12:22:13.885218Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.885494Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.885890Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d06/wp_woocommerce_tax_rate_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.886620Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d06/wp_woocommerce_tax_rate_locations` because it could not be opened.
2025-06-10T12:22:13.887092Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.887346Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.887698Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.888126Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d06\wp_woocommerce_tax_rates.ibd' OS error: 103
2025-06-10T12:22:13.888472Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.888722Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.889226Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d06/wp_woocommerce_tax_rates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.889782Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d06/wp_woocommerce_tax_rates` because it could not be opened.
2025-06-10T12:22:13.890265Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.890531Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.890987Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.891399Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d07\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:13.891725Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.892036Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.892456Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d07/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.893134Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d07/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:13.893596Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.893852Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.894169Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.894724Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d07\wp_comments.ibd' OS error: 103
2025-06-10T12:22:13.895067Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.895319Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.895706Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d07/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.896305Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d07/wp_comments` because it could not be opened.
2025-06-10T12:22:13.896659Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.896995Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.897611Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.898078Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d07\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:13.898428Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.898925Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.899393Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d07/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.900027Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d07/wp_fbv` because it could not be opened.
2025-06-10T12:22:13.900564Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.901051Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.901549Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.901941Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d07\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:13.902834Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.903100Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.903581Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d07/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.904233Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d07/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:13.904732Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.905000Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.905289Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.905717Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d07\wp_kbp_countdown_entry.ibd' OS error: 103
2025-06-10T12:22:13.906065Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.906371Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.906980Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d07/wp_kbp_countdown_entry`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.907783Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d07/wp_kbp_countdown_entry` because it could not be opened.
2025-06-10T12:22:13.908241Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.908555Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.908830Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.909220Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d07\wp_kbp_form_entry.ibd' OS error: 103
2025-06-10T12:22:13.909593Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.909926Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.910546Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d07/wp_kbp_form_entry`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.911191Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d07/wp_kbp_form_entry` because it could not be opened.
2025-06-10T12:22:13.911679Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.912054Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.912571Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.913098Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d07\wp_kbp_form_entrymeta.ibd' OS error: 103
2025-06-10T12:22:13.913600Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.913892Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.914557Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d07/wp_kbp_form_entrymeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.915207Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d07/wp_kbp_form_entrymeta` because it could not be opened.
2025-06-10T12:22:13.915825Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.916106Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.916491Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.916891Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d07\wp_links.ibd' OS error: 103
2025-06-10T12:22:13.917193Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.917705Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.918157Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d07/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.918705Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d07/wp_links` because it could not be opened.
2025-06-10T12:22:13.919177Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.919510Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.919851Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.920265Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d07\wp_options.ibd' OS error: 103
2025-06-10T12:22:13.920589Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.920858Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.921338Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d07/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.921896Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d07/wp_options` because it could not be opened.
2025-06-10T12:22:13.922333Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.922613Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.922887Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.923290Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d07\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:13.923610Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.923874Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.924314Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d07/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.924924Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d07/wp_postmeta` because it could not be opened.
2025-06-10T12:22:13.925335Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.925612Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.926054Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.926559Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d07\wp_posts.ibd' OS error: 103
2025-06-10T12:22:13.926858Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.927178Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.927588Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d07/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.928157Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d07/wp_posts` because it could not be opened.
2025-06-10T12:22:13.928530Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.928780Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.929113Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.929587Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d07\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:13.929949Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.930311Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.930900Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d07/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.931693Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d07/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:13.932178Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.932690Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.933294Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.934053Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d07\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:13.934899Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.935313Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.936014Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d07/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.936897Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d07/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:13.937610Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.938025Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.938463Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.939076Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d07\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:13.939621Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.940028Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.940698Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d07/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.941562Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d07/wp_termmeta` because it could not be opened.
2025-06-10T12:22:13.942226Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.942674Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.943102Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.943568Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d07\wp_terms.ibd' OS error: 103
2025-06-10T12:22:13.943884Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.944146Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.944604Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d07/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.945153Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d07/wp_terms` because it could not be opened.
2025-06-10T12:22:13.945564Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.945830Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.946101Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.946555Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d07\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:13.946877Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.947140Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.947608Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d07/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.948162Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d07/wp_usermeta` because it could not be opened.
2025-06-10T12:22:13.948580Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.948867Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.949154Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.949640Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d07\wp_users.ibd' OS error: 103
2025-06-10T12:22:13.949984Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.950249Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.950728Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d07/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.951247Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d07/wp_users` because it could not be opened.
2025-06-10T12:22:13.951782Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.952052Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.952358Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.952744Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d07\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:13.953092Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.953441Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.953904Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d07/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.954579Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d07/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:13.955012Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.955340Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.955617Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.956002Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d07\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:13.956405Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.956666Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.957072Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d07/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.957664Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d07/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:13.958056Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.958372Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.958639Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.959006Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d07\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:13.959356Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.959603Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.960020Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d07/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.960653Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d07/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:13.961007Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.961343Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.961616Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.962232Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d07\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:13.962582Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.963130Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.963645Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d07/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.964256Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d07/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:13.964750Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.965299Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.965571Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.966100Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d08\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:13.966427Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.966818Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.967270Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d08/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.967898Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d08/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:13.968306Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.968636Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.969211Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.969729Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d08\wp_comments.ibd' OS error: 103
2025-06-10T12:22:13.970069Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.970330Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.970857Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d08/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.971539Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d08/wp_comments` because it could not be opened.
2025-06-10T12:22:13.971978Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.972248Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.972577Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.972960Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d08\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:13.973273Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.973655Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.974073Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d08/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.974700Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d08/wp_fbv` because it could not be opened.
2025-06-10T12:22:13.975106Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.975431Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.975751Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.976116Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d08\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:13.976447Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.976801Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.977198Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d08/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.977819Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d08/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:13.978200Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.978451Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.978798Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.979165Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d08\wp_kbp_countdown_entry.ibd' OS error: 103
2025-06-10T12:22:13.979533Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.979820Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.980201Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d08/wp_kbp_countdown_entry`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.980955Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d08/wp_kbp_countdown_entry` because it could not be opened.
2025-06-10T12:22:13.981683Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.982088Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.982532Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.982977Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d08\wp_kbp_form_entry.ibd' OS error: 103
2025-06-10T12:22:13.983307Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.983646Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.984082Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d08/wp_kbp_form_entry`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.984682Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d08/wp_kbp_form_entry` because it could not be opened.
2025-06-10T12:22:13.985063Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.985315Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.985697Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.986094Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d08\wp_kbp_form_entrymeta.ibd' OS error: 103
2025-06-10T12:22:13.986538Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.986796Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.987188Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d08/wp_kbp_form_entrymeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.987825Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d08/wp_kbp_form_entrymeta` because it could not be opened.
2025-06-10T12:22:13.988202Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.988495Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.988770Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.989133Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d08\wp_links.ibd' OS error: 103
2025-06-10T12:22:13.989451Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.989794Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.990189Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d08/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.990838Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d08/wp_links` because it could not be opened.
2025-06-10T12:22:13.991180Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.991460Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.991752Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.992111Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d08\wp_options.ibd' OS error: 103
2025-06-10T12:22:13.992409Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.992760Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.993156Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d08/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.993775Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d08/wp_options` because it could not be opened.
2025-06-10T12:22:13.994138Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.994401Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.994696Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.995077Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d08\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:13.995390Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.995683Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.996091Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d08/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.996676Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d08/wp_postmeta` because it could not be opened.
2025-06-10T12:22:13.997033Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:13.997297Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:13.997593Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:13.997973Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d08\wp_posts.ibd' OS error: 103
2025-06-10T12:22:13.998283Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:13.998571Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:13.998974Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d08/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:13.999566Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d08/wp_posts` because it could not be opened.
2025-06-10T12:22:13.999895Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.000146Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.000400Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.000822Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d08\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:14.001145Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.001394Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.001862Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d08/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.002441Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d08/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:14.002936Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.003190Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.003536Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.003981Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d08\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:14.004348Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.004775Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.005250Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d08/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.005968Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d08/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:14.006354Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.006703Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.006961Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.007329Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d08\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:14.007784Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.008032Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.008545Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d08/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.009068Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d08/wp_termmeta` because it could not be opened.
2025-06-10T12:22:14.009477Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.009742Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.009992Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.010506Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d08\wp_terms.ibd' OS error: 103
2025-06-10T12:22:14.011358Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.011642Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.012197Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d08/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.012801Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d08/wp_terms` because it could not be opened.
2025-06-10T12:22:14.013662Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.013928Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.014511Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.014998Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d08\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:14.015364Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.015635Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.016063Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d08/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.016607Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d08/wp_usermeta` because it could not be opened.
2025-06-10T12:22:14.017086Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.017361Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.017633Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.018083Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d08\wp_users.ibd' OS error: 103
2025-06-10T12:22:14.018422Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.018726Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.019184Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d08/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.019960Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d08/wp_users` because it could not be opened.
2025-06-10T12:22:14.020457Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.020725Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.021113Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.021512Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d08\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:14.021854Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.022319Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.022756Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d08/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.023419Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d08/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:14.023859Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.024251Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.024580Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.025136Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d08\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:14.025519Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.025840Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.026322Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d08/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.026883Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d08/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:14.027344Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.027610Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.027876Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.028318Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d08\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:14.028639Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.028945Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.029374Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d08/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.030015Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d08/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:14.030402Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.030660Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.030995Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.031526Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d08\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:14.031930Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.032207Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.032614Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d08/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.033438Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d08/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:14.033906Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.034182Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.034457Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.034840Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d09\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:14.035223Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.035488Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.035961Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d09/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.036535Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d09/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:14.036988Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.037259Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.037526Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.037975Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d09\wp_comments.ibd' OS error: 103
2025-06-10T12:22:14.038294Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.038557Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.039011Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d09/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.039563Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d09/wp_comments` because it could not be opened.
2025-06-10T12:22:14.039969Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.040234Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.040504Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.040926Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d09\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:14.041245Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.041504Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.042016Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d09/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.043258Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d09/wp_fbv` because it could not be opened.
2025-06-10T12:22:14.044408Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.045296Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.045928Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.046412Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d09\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:14.046789Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.047067Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.047543Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d09/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.048127Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d09/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:14.048635Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.048928Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.049192Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.049680Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d09\wp_kbp_countdown_entry.ibd' OS error: 103
2025-06-10T12:22:14.050052Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.050300Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.050809Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d09/wp_kbp_countdown_entry`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.051485Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d09/wp_kbp_countdown_entry` because it could not be opened.
2025-06-10T12:22:14.051940Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.052217Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.052569Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.052958Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d09\wp_kbp_form_entry.ibd' OS error: 103
2025-06-10T12:22:14.053295Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.053645Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.054132Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d09/wp_kbp_form_entry`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.054760Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d09/wp_kbp_form_entry` because it could not be opened.
2025-06-10T12:22:14.055182Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.055502Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.055919Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.056344Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d09\wp_kbp_form_entrymeta.ibd' OS error: 103
2025-06-10T12:22:14.056751Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.057079Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.057533Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d09/wp_kbp_form_entrymeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.058080Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d09/wp_kbp_form_entrymeta` because it could not be opened.
2025-06-10T12:22:14.058539Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.058796Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.059055Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.059476Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d09\wp_links.ibd' OS error: 103
2025-06-10T12:22:14.059776Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.060025Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.060575Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d09/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.061100Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d09/wp_links` because it could not be opened.
2025-06-10T12:22:14.061523Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.061903Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.062194Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.062671Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d09\wp_options.ibd' OS error: 103
2025-06-10T12:22:14.062976Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.063226Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.063775Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d09/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.064355Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d09/wp_options` because it could not be opened.
2025-06-10T12:22:14.064763Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.065016Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.065314Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.065800Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d09\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:14.066105Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.066428Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.066823Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d09/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.067448Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d09/wp_postmeta` because it could not be opened.
2025-06-10T12:22:14.067862Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.068125Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.068532Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.068958Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d09\wp_posts.ibd' OS error: 103
2025-06-10T12:22:14.069285Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.069660Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.070047Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d09/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.070694Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d09/wp_posts` because it could not be opened.
2025-06-10T12:22:14.071057Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.071362Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.071636Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.071994Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d09\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:14.072369Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.072631Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.073018Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d09/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.073668Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d09/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:14.074248Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.075849Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.076815Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.077428Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d09\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:14.078357Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.078623Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.079114Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d09/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.079705Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d09/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:14.080120Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.080382Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.080689Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.081076Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d09\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:14.081387Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.081685Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.082101Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d09/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.082676Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d09/wp_termmeta` because it could not be opened.
2025-06-10T12:22:14.083080Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.083466Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.083812Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.084185Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d09\wp_terms.ibd' OS error: 103
2025-06-10T12:22:14.084487Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.084822Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.085255Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d09/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.085935Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d09/wp_terms` because it could not be opened.
2025-06-10T12:22:14.086356Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.086686Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.087015Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.087389Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d09\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:14.087751Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.088020Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.088417Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d09/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.089012Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d09/wp_usermeta` because it could not be opened.
2025-06-10T12:22:14.089387Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.089670Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.090052Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.090476Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d09\wp_users.ibd' OS error: 103
2025-06-10T12:22:14.090835Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.091098Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.091524Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d09/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.092116Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d09/wp_users` because it could not be opened.
2025-06-10T12:22:14.092500Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.092804Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.093079Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.093553Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d09\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:14.094027Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.094327Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.094808Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d09/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.095372Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d09/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:14.095882Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.096175Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.096430Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.096870Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d09\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:14.097326Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.097582Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.098106Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d09/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.098723Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d09/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:14.099113Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.099366Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.099672Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.100054Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d09\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:14.100367Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.100734Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.101171Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d09/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.101808Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d09/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:14.102525Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.102874Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.103165Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.103533Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d09\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:14.104074Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.104339Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.104814Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d09/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.105372Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d09/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:14.105888Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.106141Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.106399Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.107560Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d10\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:14.108688Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.109723Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.110790Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d10/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.111433Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d10/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:14.111918Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.112396Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.112697Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.113070Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d10\wp_comments.ibd' OS error: 103
2025-06-10T12:22:14.113395Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.113648Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.114042Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d10/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.114764Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d10/wp_comments` because it could not be opened.
2025-06-10T12:22:14.115198Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.115490Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.115751Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.116123Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d10\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:14.116537Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.116794Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.117297Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d10/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.117968Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d10/wp_fbv` because it could not be opened.
2025-06-10T12:22:14.118606Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.118943Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.119327Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.119714Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d10\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:14.120048Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.120350Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.120743Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d10/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.121413Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d10/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:14.121812Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.122065Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.122482Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.122849Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d10\wp_kbp_countdown_entry.ibd' OS error: 103
2025-06-10T12:22:14.123234Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.123509Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.123907Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d10/wp_kbp_countdown_entry`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.124555Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d10/wp_kbp_countdown_entry` because it could not be opened.
2025-06-10T12:22:14.124938Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.125375Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.125693Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.126085Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d10\wp_kbp_form_entry.ibd' OS error: 103
2025-06-10T12:22:14.126443Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.126709Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.127144Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d10/wp_kbp_form_entry`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.127739Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d10/wp_kbp_form_entry` because it could not be opened.
2025-06-10T12:22:14.128181Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.128454Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.128729Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.129138Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d10\wp_kbp_form_entrymeta.ibd' OS error: 103
2025-06-10T12:22:14.129490Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.129762Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.130216Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d10/wp_kbp_form_entrymeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.130820Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d10/wp_kbp_form_entrymeta` because it could not be opened.
2025-06-10T12:22:14.131245Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.131516Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.131792Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.132209Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d10\wp_links.ibd' OS error: 103
2025-06-10T12:22:14.132534Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.132804Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.133289Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d10/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.133856Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d10/wp_links` because it could not be opened.
2025-06-10T12:22:14.134293Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.134576Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.134852Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.135257Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d10\wp_options.ibd' OS error: 103
2025-06-10T12:22:14.135579Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.135843Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.136283Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d10/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.136838Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d10/wp_options` because it could not be opened.
2025-06-10T12:22:14.137230Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.137521Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.137795Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.138217Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d10\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:14.138650Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.138916Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.139819Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d10/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.140461Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d10/wp_postmeta` because it could not be opened.
2025-06-10T12:22:14.140866Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.141859Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.142563Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.142977Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d10\wp_posts.ibd' OS error: 103
2025-06-10T12:22:14.143317Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.143617Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.144033Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d10/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.144612Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d10/wp_posts` because it could not be opened.
2025-06-10T12:22:14.145355Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.145681Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.145948Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.146320Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d10\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:14.146749Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.147077Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.147548Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d10/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.148167Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d10/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:14.148683Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.148963Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.149237Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.149676Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d10\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:14.150025Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.150290Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.150749Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d10/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.151460Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d10/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:14.151944Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.152216Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.152502Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.152905Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d10\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:14.153219Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.153480Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.153929Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d10/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.154500Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d10/wp_termmeta` because it could not be opened.
2025-06-10T12:22:14.154914Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.155179Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.155449Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.155857Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d10\wp_terms.ibd' OS error: 103
2025-06-10T12:22:14.156165Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.156424Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.156874Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d10/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.157441Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d10/wp_terms` because it could not be opened.
2025-06-10T12:22:14.157839Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.158105Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.158375Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.158798Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d10\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:14.159113Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.159371Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.159826Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d10/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.160383Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d10/wp_usermeta` because it could not be opened.
2025-06-10T12:22:14.160781Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.161044Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.161313Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.161732Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d10\wp_users.ibd' OS error: 103
2025-06-10T12:22:14.162046Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.162444Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.163000Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d10/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.163597Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d10/wp_users` because it could not be opened.
2025-06-10T12:22:14.163986Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.164270Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.164569Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.164951Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d10\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:14.165345Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.165640Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.166049Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d10/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.166666Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d10/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:14.167074Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.167340Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.167642Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.168019Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d10\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:14.168343Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.168836Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.169280Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d10/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.169880Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d10/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:14.170791Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.171064Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.171483Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.171872Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d10\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:14.172353Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.172613Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.173074Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d10/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.174061Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d10/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:14.174744Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.175020Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.175320Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.175932Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d10\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:14.176337Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.176610Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.177118Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d10/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.177777Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d10/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:14.178250Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.178519Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.178873Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.179334Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d11\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:14.179665Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.180013Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.180431Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d11/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.181102Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d11/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:14.181537Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.181892Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.182270Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.182689Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d11\wp_comments.ibd' OS error: 103
2025-06-10T12:22:14.183042Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.183297Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.183693Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d11/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.184357Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d11/wp_comments` because it could not be opened.
2025-06-10T12:22:14.184782Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.185056Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.185330Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.185805Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d11\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:14.186135Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.186385Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.186867Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d11/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.187398Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d11/wp_fbv` because it could not be opened.
2025-06-10T12:22:14.187797Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.188071Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.188418Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.188876Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d11\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:14.189242Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.189507Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.189981Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d11/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.190567Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d11/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:14.191025Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.191290Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.191561Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.192011Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d11\wp_kbp_countdown_entry.ibd' OS error: 103
2025-06-10T12:22:14.192353Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.192615Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.193088Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d11/wp_kbp_countdown_entry`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.193664Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d11/wp_kbp_countdown_entry` because it could not be opened.
2025-06-10T12:22:14.194234Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.194494Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.194829Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.195197Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d11\wp_kbp_form_entry.ibd' OS error: 103
2025-06-10T12:22:14.195512Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.195833Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.196225Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d11/wp_kbp_form_entry`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.196836Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d11/wp_kbp_form_entry` because it could not be opened.
2025-06-10T12:22:14.197261Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.197513Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.197855Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.198368Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d11\wp_kbp_form_entrymeta.ibd' OS error: 103
2025-06-10T12:22:14.198731Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.199025Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.199417Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d11/wp_kbp_form_entrymeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.200068Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d11/wp_kbp_form_entrymeta` because it could not be opened.
2025-06-10T12:22:14.200553Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.200960Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.201312Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.201775Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d11\wp_links.ibd' OS error: 103
2025-06-10T12:22:14.202091Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.202338Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.202789Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d11/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.203407Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d11/wp_links` because it could not be opened.
2025-06-10T12:22:14.203970Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.204259Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.204536Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.205032Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d11\wp_options.ibd' OS error: 103
2025-06-10T12:22:14.205352Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.205617Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.206092Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d11/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.206684Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d11/wp_options` because it could not be opened.
2025-06-10T12:22:14.207102Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.207367Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.207721Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.208150Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d11\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:14.208482Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.208780Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.209186Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d11/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.209765Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d11/wp_postmeta` because it could not be opened.
2025-06-10T12:22:14.210164Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.210417Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.210726Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.211108Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d11\wp_posts.ibd' OS error: 103
2025-06-10T12:22:14.211404Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.211694Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.212183Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d11/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.212858Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d11/wp_posts` because it could not be opened.
2025-06-10T12:22:14.213265Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.213533Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.213879Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.214264Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d11\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:14.214598Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.214920Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.215331Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d11/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.215967Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d11/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:14.216354Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.216672Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.216957Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.217333Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d11\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:14.217717Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.217981Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.218512Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d11/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.219795Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d11/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:14.220854Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.221513Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.221824Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.222317Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d11\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:14.222768Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.223038Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.223495Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d11/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.224081Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d11/wp_termmeta` because it could not be opened.
2025-06-10T12:22:14.224517Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.224787Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.225057Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.225500Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d11\wp_terms.ibd' OS error: 103
2025-06-10T12:22:14.225818Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.226080Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.226697Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d11/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.227280Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d11/wp_terms` because it could not be opened.
2025-06-10T12:22:14.227694Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.227965Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.228267Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.228688Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d11\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:14.229005Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.229301Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.229737Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d11/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.230326Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d11/wp_usermeta` because it could not be opened.
2025-06-10T12:22:14.230803Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.231119Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.231458Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.231840Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d11\wp_users.ibd' OS error: 103
2025-06-10T12:22:14.232281Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.232579Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.232993Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d11/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.233564Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d11/wp_users` because it could not be opened.
2025-06-10T12:22:14.233957Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.234256Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.234554Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.234937Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d11\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:14.235306Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.235568Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.235979Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d11/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.236589Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d11/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:14.236985Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.237282Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.237555Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.237934Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d11\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:14.238392Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.238683Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.239102Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d11/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.239700Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d11/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:14.240092Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.240399Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.240668Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.241053Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d11\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:14.241413Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.241677Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.242088Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d11/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.242683Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d11/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:14.243046Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.243405Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.243848Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.244256Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_d11\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:14.244640Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.244940Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.245451Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_d11/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.246065Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_d11/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:14.246537Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.246807Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.247146Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.247556Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_resource\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:14.247881Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.248131Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.248637Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_resource/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.249227Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_resource/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:14.249681Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.249967Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.250255Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.250719Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_resource\wp_comments.ibd' OS error: 103
2025-06-10T12:22:14.251045Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.251422Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.251975Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_resource/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.253912Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_resource/wp_comments` because it could not be opened.
2025-06-10T12:22:14.255163Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.255625Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.255989Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.256435Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_resource\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:14.256763Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.257053Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.257506Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_resource/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.258143Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_resource/wp_fbv` because it could not be opened.
2025-06-10T12:22:14.258566Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.258832Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.259140Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.259535Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_resource\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:14.259925Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.260286Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.260733Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_resource/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.261365Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_resource/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:14.261877Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.262169Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.262441Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.262825Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_resource\wp_links.ibd' OS error: 103
2025-06-10T12:22:14.263234Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.263503Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.263965Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_resource/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.264524Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_resource/wp_links` because it could not be opened.
2025-06-10T12:22:14.264963Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.265235Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.265503Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.265906Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_resource\wp_options.ibd' OS error: 103
2025-06-10T12:22:14.266234Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.266491Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.266942Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_resource/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.267496Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_resource/wp_options` because it could not be opened.
2025-06-10T12:22:14.267908Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.268176Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.268444Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.268819Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_resource\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:14.269196Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.269461Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.269887Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_resource/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.270444Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_resource/wp_postmeta` because it could not be opened.
2025-06-10T12:22:14.270854Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.271134Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.271398Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.271776Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_resource\wp_posts.ibd' OS error: 103
2025-06-10T12:22:14.272120Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.272377Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.273018Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_resource/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.273577Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_resource/wp_posts` because it could not be opened.
2025-06-10T12:22:14.274018Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.274324Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.274580Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.275013Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_resource\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:14.275397Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.275644Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.276128Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_resource/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.276699Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_resource/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:14.277286Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.277546Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.277831Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.278233Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_resource\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:14.278555Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.278837Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.279337Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_resource/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.279943Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_resource/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:14.280448Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.280699Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.281018Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.281441Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_resource\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:14.281797Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.282087Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.284532Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_resource/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.285448Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_resource/wp_termmeta` because it could not be opened.
2025-06-10T12:22:14.286181Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.286624Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.287191Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.287603Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_resource\wp_terms.ibd' OS error: 103
2025-06-10T12:22:14.287952Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.288245Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.288710Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_resource/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.289292Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_resource/wp_terms` because it could not be opened.
2025-06-10T12:22:14.289719Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.289986Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.290257Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.290704Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_resource\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:14.291062Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.291324Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.291952Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_resource/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.292575Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_resource/wp_usermeta` because it could not be opened.
2025-06-10T12:22:14.293023Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.293291Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.293597Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.293997Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_resource\wp_users.ibd' OS error: 103
2025-06-10T12:22:14.294326Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.294632Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.295270Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_resource/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.295944Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_resource/wp_users` because it could not be opened.
2025-06-10T12:22:14.296354Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.296673Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.296934Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.297297Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_resource\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:14.297756Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.298070Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.298472Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_resource/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.299086Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_resource/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:14.299481Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.299846Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.300114Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.300477Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_resource\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:14.300851Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.301099Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.301537Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_resource/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.302116Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_resource/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:14.302531Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.302844Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.303101Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.303462Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_resource\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:14.303837Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.304082Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.304467Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_resource/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.305092Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_resource/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:14.305454Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.305771Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.306039Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.306411Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_resource\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:14.306825Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.307084Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.307514Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_resource/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.308142Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_resource/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:14.308685Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.308959Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.309210Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.309645Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb01\wp_actionscheduler_actions.ibd' OS error: 103
2025-06-10T12:22:14.309979Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.310228Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.310743Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb01/wp_actionscheduler_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.311588Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb01/wp_actionscheduler_actions` because it could not be opened.
2025-06-10T12:22:14.312009Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.312262Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.312569Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.313021Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb01\wp_actionscheduler_claims.ibd' OS error: 103
2025-06-10T12:22:14.313352Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.313662Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.314282Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb01/wp_actionscheduler_claims`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.316007Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb01/wp_actionscheduler_claims` because it could not be opened.
2025-06-10T12:22:14.317034Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.318066Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.318541Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.318969Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb01\wp_actionscheduler_groups.ibd' OS error: 103
2025-06-10T12:22:14.319324Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.319640Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.320090Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb01/wp_actionscheduler_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.320739Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb01/wp_actionscheduler_groups` because it could not be opened.
2025-06-10T12:22:14.321182Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.321488Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.321766Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.322155Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb01\wp_actionscheduler_logs.ibd' OS error: 103
2025-06-10T12:22:14.322533Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.322800Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.323285Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb01/wp_actionscheduler_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.324166Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb01/wp_actionscheduler_logs` because it could not be opened.
2025-06-10T12:22:14.324677Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.324950Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.325223Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.325658Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb01\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:14.325998Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.326260Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.326908Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb01/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.327524Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb01/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:14.327951Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.328216Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.328530Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.328913Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb01\wp_comments.ibd' OS error: 103
2025-06-10T12:22:14.329232Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.329535Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.330020Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb01/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.330639Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb01/wp_comments` because it could not be opened.
2025-06-10T12:22:14.331042Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.331311Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.331630Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.332014Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb01\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:14.332336Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.332617Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.333030Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb01/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.333654Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb01/wp_fbv` because it could not be opened.
2025-06-10T12:22:14.334046Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.334323Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.334616Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.335004Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb01\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:14.335399Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.335676Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.336169Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb01/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.336829Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb01/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:14.337272Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.337573Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.337864Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.338251Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb01\wp_links.ibd' OS error: 103
2025-06-10T12:22:14.338608Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.338874Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.339282Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb01/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.339873Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb01/wp_links` because it could not be opened.
2025-06-10T12:22:14.340323Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.340636Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.340915Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.341310Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb01\wp_options.ibd' OS error: 103
2025-06-10T12:22:14.341702Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.341965Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.342413Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb01/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.343060Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb01/wp_options` because it could not be opened.
2025-06-10T12:22:14.343544Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.343808Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.344075Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.344540Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb01\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:14.344848Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.345099Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.345575Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb01/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.346346Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb01/wp_postmeta` because it could not be opened.
2025-06-10T12:22:14.346886Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.347229Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.347503Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.347914Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb01\wp_posts.ibd' OS error: 103
2025-06-10T12:22:14.348228Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.348578Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.349187Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb01/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.349911Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb01/wp_posts` because it could not be opened.
2025-06-10T12:22:14.350522Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.350925Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.351205Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.351667Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb01\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:14.352049Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.352310Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.352750Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb01/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.353358Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb01/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:14.353818Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.354113Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.354386Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.354794Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb01\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:14.355143Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.355405Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.356065Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb01/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.356678Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb01/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:14.357452Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.358048Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.358515Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.359207Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb01\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:14.359697Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.360153Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.360682Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb01/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.361322Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb01/wp_termmeta` because it could not be opened.
2025-06-10T12:22:14.361739Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.362019Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.362288Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.362673Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb01\wp_terms.ibd' OS error: 103
2025-06-10T12:22:14.363176Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.363465Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.363963Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb01/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.364599Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb01/wp_terms` because it could not be opened.
2025-06-10T12:22:14.365092Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.365349Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.365668Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.366097Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb01\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:14.366422Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.366687Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.367137Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb01/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.367695Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb01/wp_usermeta` because it could not be opened.
2025-06-10T12:22:14.368142Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.368413Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.368684Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.369143Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb01\wp_users.ibd' OS error: 103
2025-06-10T12:22:14.369484Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.369767Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.370179Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb01/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.370705Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb01/wp_users` because it could not be opened.
2025-06-10T12:22:14.371262Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.371583Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.371922Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.372314Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb01\wp_wc_admin_note_actions.ibd' OS error: 103
2025-06-10T12:22:14.372663Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.372983Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.373413Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb01/wp_wc_admin_note_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.374082Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb01/wp_wc_admin_note_actions` because it could not be opened.
2025-06-10T12:22:14.374545Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.374894Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.375157Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.375620Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb01\wp_wc_admin_notes.ibd' OS error: 103
2025-06-10T12:22:14.376023Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.376292Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.376724Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb01/wp_wc_admin_notes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.377303Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb01/wp_wc_admin_notes` because it could not be opened.
2025-06-10T12:22:14.377732Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.378014Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.378286Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.378669Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb01\wp_wc_category_lookup.ibd' OS error: 103
2025-06-10T12:22:14.379044Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.379304Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.379841Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb01/wp_wc_category_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.381026Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb01/wp_wc_category_lookup` because it could not be opened.
2025-06-10T12:22:14.381768Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.382206Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.382742Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.383790Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb01\wp_wc_customer_lookup.ibd' OS error: 103
2025-06-10T12:22:14.384500Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.384796Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.385274Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb01/wp_wc_customer_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.385860Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb01/wp_wc_customer_lookup` because it could not be opened.
2025-06-10T12:22:14.386499Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.386815Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.387156Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.387552Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb01\wp_wc_download_log.ibd' OS error: 103
2025-06-10T12:22:14.387888Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.388226Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.388653Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb01/wp_wc_download_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.389329Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb01/wp_wc_download_log` because it could not be opened.
2025-06-10T12:22:14.389818Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.390172Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.390457Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.390840Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb01\wp_wc_order_coupon_lookup.ibd' OS error: 103
2025-06-10T12:22:14.391324Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.391633Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.392079Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb01/wp_wc_order_coupon_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.392731Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb01/wp_wc_order_coupon_lookup` because it could not be opened.
2025-06-10T12:22:14.393231Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.393506Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.393779Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.394206Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb01\wp_wc_order_product_lookup.ibd' OS error: 103
2025-06-10T12:22:14.394557Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.394820Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.395284Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb01/wp_wc_order_product_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.395873Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb01/wp_wc_order_product_lookup` because it could not be opened.
2025-06-10T12:22:14.396326Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.396592Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.396873Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.397301Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb01\wp_wc_order_stats.ibd' OS error: 103
2025-06-10T12:22:14.397637Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.397991Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.398476Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb01/wp_wc_order_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.399094Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb01/wp_wc_order_stats` because it could not be opened.
2025-06-10T12:22:14.399545Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.399799Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.400104Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.400495Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb01\wp_wc_order_tax_lookup.ibd' OS error: 103
2025-06-10T12:22:14.400826Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.401155Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.401565Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb01/wp_wc_order_tax_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.402173Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb01/wp_wc_order_tax_lookup` because it could not be opened.
2025-06-10T12:22:14.402663Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.402923Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.403283Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.403647Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb01\wp_wc_product_meta_lookup.ibd' OS error: 103
2025-06-10T12:22:14.404354Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.404633Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.405065Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb01/wp_wc_product_meta_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.405653Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb01/wp_wc_product_meta_lookup` because it could not be opened.
2025-06-10T12:22:14.406121Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.406389Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.406657Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.407043Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb01\wp_wc_rate_limits.ibd' OS error: 103
2025-06-10T12:22:14.407435Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.407696Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.408133Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb01/wp_wc_rate_limits`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.408696Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb01/wp_wc_rate_limits` because it could not be opened.
2025-06-10T12:22:14.409124Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.409393Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.409660Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.410125Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb01\wp_wc_reserved_stock.ibd' OS error: 103
2025-06-10T12:22:14.410496Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.410752Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.411250Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb01/wp_wc_reserved_stock`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.411788Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb01/wp_wc_reserved_stock` because it could not be opened.
2025-06-10T12:22:14.412233Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.412489Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.412750Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.413248Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb01\wp_wc_tax_rate_classes.ibd' OS error: 103
2025-06-10T12:22:14.413586Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.413841Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.414288Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb01/wp_wc_tax_rate_classes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.414858Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb01/wp_wc_tax_rate_classes` because it could not be opened.
2025-06-10T12:22:14.415280Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.415541Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.415812Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.416386Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb01\wp_wc_webhooks.ibd' OS error: 103
2025-06-10T12:22:14.416721Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.416975Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.417450Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb01/wp_wc_webhooks`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.417997Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb01/wp_wc_webhooks` because it could not be opened.
2025-06-10T12:22:14.418652Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.418904Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.419281Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.419656Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb01\wp_woocommerce_api_keys.ibd' OS error: 103
2025-06-10T12:22:14.420125Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.420416Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.421065Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb01/wp_woocommerce_api_keys`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.421771Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb01/wp_woocommerce_api_keys` because it could not be opened.
2025-06-10T12:22:14.422296Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.422616Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.423073Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.423640Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb01\wp_woocommerce_attribute_taxonomies.ibd' OS error: 103
2025-06-10T12:22:14.424197Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.424442Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.424830Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb01/wp_woocommerce_attribute_taxonomies`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.425634Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb01/wp_woocommerce_attribute_taxonomies` because it could not be opened.
2025-06-10T12:22:14.426127Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.426397Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.426652Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.427722Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb01\wp_woocommerce_downloadable_product_permissions.ibd' OS error: 103
2025-06-10T12:22:14.429380Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.430392Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.431049Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb01/wp_woocommerce_downloadable_product_permissions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.432304Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb01/wp_woocommerce_downloadable_product_permissions` because it could not be opened.
2025-06-10T12:22:14.432955Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.433301Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.433621Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.434003Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb01\wp_woocommerce_log.ibd' OS error: 103
2025-06-10T12:22:14.434363Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.434622Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.435041Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb01/wp_woocommerce_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.435740Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb01/wp_woocommerce_log` because it could not be opened.
2025-06-10T12:22:14.436205Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.436487Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.436762Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.437221Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb01\wp_woocommerce_order_itemmeta.ibd' OS error: 103
2025-06-10T12:22:14.437587Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.437850Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.438326Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb01/wp_woocommerce_order_itemmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.438944Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb01/wp_woocommerce_order_itemmeta` because it could not be opened.
2025-06-10T12:22:14.439445Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.439729Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.439999Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.440409Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb01\wp_woocommerce_order_items.ibd' OS error: 103
2025-06-10T12:22:14.440806Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.441134Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.441602Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb01/wp_woocommerce_order_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.442253Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb01/wp_woocommerce_order_items` because it could not be opened.
2025-06-10T12:22:14.442811Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.443065Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.443447Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.443818Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb01\wp_woocommerce_payment_tokenmeta.ibd' OS error: 103
2025-06-10T12:22:14.444229Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.444481Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.444875Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb01/wp_woocommerce_payment_tokenmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.445538Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb01/wp_woocommerce_payment_tokenmeta` because it could not be opened.
2025-06-10T12:22:14.445940Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.446260Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.446519Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.446885Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb01\wp_woocommerce_payment_tokens.ibd' OS error: 103
2025-06-10T12:22:14.447315Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.447579Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.447992Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb01/wp_woocommerce_payment_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.448598Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb01/wp_woocommerce_payment_tokens` because it could not be opened.
2025-06-10T12:22:14.448997Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.449333Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.449592Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.449957Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb01\wp_woocommerce_sessions.ibd' OS error: 103
2025-06-10T12:22:14.450354Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.450622Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.451047Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb01/wp_woocommerce_sessions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.451661Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb01/wp_woocommerce_sessions` because it could not be opened.
2025-06-10T12:22:14.452121Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.452399Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.452669Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.453092Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb01\wp_woocommerce_shipping_zone_locations.ibd' OS error: 103
2025-06-10T12:22:14.453478Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.453744Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.454245Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb01/wp_woocommerce_shipping_zone_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.454864Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb01/wp_woocommerce_shipping_zone_locations` because it could not be opened.
2025-06-10T12:22:14.455345Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.455609Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.455879Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.456314Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb01\wp_woocommerce_shipping_zone_methods.ibd' OS error: 103
2025-06-10T12:22:14.456688Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.456963Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.457405Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb01/wp_woocommerce_shipping_zone_methods`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.458040Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb01/wp_woocommerce_shipping_zone_methods` because it could not be opened.
2025-06-10T12:22:14.458487Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.458750Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.459032Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.459465Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb01\wp_woocommerce_shipping_zones.ibd' OS error: 103
2025-06-10T12:22:14.459826Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.460143Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.460558Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb01/wp_woocommerce_shipping_zones`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.461202Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb01/wp_woocommerce_shipping_zones` because it could not be opened.
2025-06-10T12:22:14.461674Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.462227Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.462584Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.463172Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb01\wp_woocommerce_tax_rate_locations.ibd' OS error: 103
2025-06-10T12:22:14.463567Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.463925Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.464558Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb01/wp_woocommerce_tax_rate_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.465482Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb01/wp_woocommerce_tax_rate_locations` because it could not be opened.
2025-06-10T12:22:14.465987Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.466273Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.466537Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.466995Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb01\wp_woocommerce_tax_rates.ibd' OS error: 103
2025-06-10T12:22:14.467343Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.467595Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.468106Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb01/wp_woocommerce_tax_rates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.468672Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb01/wp_woocommerce_tax_rates` because it could not be opened.
2025-06-10T12:22:14.469203Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.469468Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.469737Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.470218Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb01\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:14.470552Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.471195Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.471649Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb01/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.472341Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb01/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:14.472925Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.473228Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.473488Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.473986Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb01\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:14.474364Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.474652Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.475168Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb01/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.475707Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb01/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:14.476183Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.476444Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.476712Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.477144Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb01\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:14.477454Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.477786Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.478236Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb01/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.478848Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb01/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:14.479214Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.479466Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.479801Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.480186Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb01\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:14.480522Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.480951Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.481388Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb01/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.482056Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb01/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:14.482549Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.482865Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.483188Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.483586Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb02\wp_actionscheduler_actions.ibd' OS error: 103
2025-06-10T12:22:14.484003Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.484287Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.484742Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb02/wp_actionscheduler_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.485381Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb02/wp_actionscheduler_actions` because it could not be opened.
2025-06-10T12:22:14.485945Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.486325Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.486738Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.487374Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb02\wp_actionscheduler_claims.ibd' OS error: 103
2025-06-10T12:22:14.487739Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.488021Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.488437Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb02/wp_actionscheduler_claims`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.489066Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb02/wp_actionscheduler_claims` because it could not be opened.
2025-06-10T12:22:14.489485Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.489786Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.490066Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.490447Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb02\wp_actionscheduler_groups.ibd' OS error: 103
2025-06-10T12:22:14.490989Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.491256Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.491788Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb02/wp_actionscheduler_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.493446Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb02/wp_actionscheduler_groups` because it could not be opened.
2025-06-10T12:22:14.493977Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.494243Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.494553Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.494974Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb02\wp_actionscheduler_logs.ibd' OS error: 103
2025-06-10T12:22:14.495321Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.495617Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.496095Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb02/wp_actionscheduler_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.496775Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb02/wp_actionscheduler_logs` because it could not be opened.
2025-06-10T12:22:14.497224Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.497528Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.497802Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.498187Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb02\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:14.498550Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.499002Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.499498Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb02/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.500065Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb02/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:14.500609Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.500917Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.501184Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.501697Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb02\wp_comments.ibd' OS error: 103
2025-06-10T12:22:14.502028Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.502356Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.502803Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb02/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.503344Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb02/wp_comments` because it could not be opened.
2025-06-10T12:22:14.503847Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.504101Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.504410Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.504825Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb02\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:14.505124Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.505381Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.505863Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb02/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.506393Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb02/wp_fbv` because it could not be opened.
2025-06-10T12:22:14.506987Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.507273Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.507610Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.507987Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb02\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:14.508433Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.508760Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.509162Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb02/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.509822Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb02/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:14.510218Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.510538Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.510801Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.511171Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb02\wp_links.ibd' OS error: 103
2025-06-10T12:22:14.511534Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.511789Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.512190Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb02/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.512830Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb02/wp_links` because it could not be opened.
2025-06-10T12:22:14.513173Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.513477Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.513791Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.514163Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb02\wp_options.ibd' OS error: 103
2025-06-10T12:22:14.514538Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.514842Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.515256Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb02/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.515846Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb02/wp_options` because it could not be opened.
2025-06-10T12:22:14.516252Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.516691Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.517106Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.517747Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb02\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:14.518234Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.518734Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.519495Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb02/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.520378Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb02/wp_postmeta` because it could not be opened.
2025-06-10T12:22:14.521026Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.521314Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.521678Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.522053Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb02\wp_posts.ibd' OS error: 103
2025-06-10T12:22:14.522486Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.522743Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.524201Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb02/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.524881Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb02/wp_posts` because it could not be opened.
2025-06-10T12:22:14.525295Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.526313Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.526585Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.527149Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb02\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:14.527536Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.527845Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.528266Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb02/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.528911Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb02/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:14.529409Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.529709Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.530061Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.530459Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb02\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:14.530826Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.531092Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.531512Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb02/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.532148Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb02/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:14.532597Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.532904Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.533182Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.533578Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb02\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:14.533940Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.534214Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.534707Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb02/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.535317Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb02/wp_termmeta` because it could not be opened.
2025-06-10T12:22:14.535771Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.536054Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.536327Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.536808Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb02\wp_terms.ibd' OS error: 103
2025-06-10T12:22:14.537122Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.537381Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.537829Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb02/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.538375Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb02/wp_terms` because it could not be opened.
2025-06-10T12:22:14.538762Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.539040Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.539311Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.539693Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb02\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:14.540050Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.540371Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.540889Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb02/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.541456Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb02/wp_usermeta` because it could not be opened.
2025-06-10T12:22:14.541864Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.542132Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.542400Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.542814Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb02\wp_users.ibd' OS error: 103
2025-06-10T12:22:14.543137Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.543397Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.543846Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb02/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.544389Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb02/wp_users` because it could not be opened.
2025-06-10T12:22:14.544786Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.545057Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.545326Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.545731Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb02\wp_wc_admin_note_actions.ibd' OS error: 103
2025-06-10T12:22:14.546114Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.546722Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.547221Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb02/wp_wc_admin_note_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.547912Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb02/wp_wc_admin_note_actions` because it could not be opened.
2025-06-10T12:22:14.548353Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.548623Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.548967Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.549349Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb02\wp_wc_admin_notes.ibd' OS error: 103
2025-06-10T12:22:14.549839Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.550165Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.550594Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb02/wp_wc_admin_notes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.551260Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb02/wp_wc_admin_notes` because it could not be opened.
2025-06-10T12:22:14.551735Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.552012Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.552281Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.552714Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb02\wp_wc_category_lookup.ibd' OS error: 103
2025-06-10T12:22:14.553214Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.553523Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.553990Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb02/wp_wc_category_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.554572Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb02/wp_wc_category_lookup` because it could not be opened.
2025-06-10T12:22:14.555093Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.555354Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.555619Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.556612Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb02\wp_wc_customer_lookup.ibd' OS error: 103
2025-06-10T12:22:14.557763Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.558355Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.558861Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb02/wp_wc_customer_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.559690Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb02/wp_wc_customer_lookup` because it could not be opened.
2025-06-10T12:22:14.560255Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.560649Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.560949Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.561359Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb02\wp_wc_download_log.ibd' OS error: 103
2025-06-10T12:22:14.561702Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.561966Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.562460Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb02/wp_wc_download_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.563065Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb02/wp_wc_download_log` because it could not be opened.
2025-06-10T12:22:14.563588Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.563840Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.564099Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.564598Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb02\wp_wc_order_coupon_lookup.ibd' OS error: 103
2025-06-10T12:22:14.564932Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.565182Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.565782Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb02/wp_wc_order_coupon_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.566459Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb02/wp_wc_order_coupon_lookup` because it could not be opened.
2025-06-10T12:22:14.566957Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.567221Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.567717Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.569561Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb02\wp_wc_order_product_lookup.ibd' OS error: 103
2025-06-10T12:22:14.570053Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.570370Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.570796Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb02/wp_wc_order_product_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.571455Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb02/wp_wc_order_product_lookup` because it could not be opened.
2025-06-10T12:22:14.571896Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.572161Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.572497Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.572880Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb02\wp_wc_order_stats.ibd' OS error: 103
2025-06-10T12:22:14.573206Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.573533Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.573944Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb02/wp_wc_order_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.574674Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb02/wp_wc_order_stats` because it could not be opened.
2025-06-10T12:22:14.575069Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.575361Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.575637Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.576003Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb02\wp_wc_order_tax_lookup.ibd' OS error: 103
2025-06-10T12:22:14.576368Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.576720Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.577145Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb02/wp_wc_order_tax_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.577841Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb02/wp_wc_order_tax_lookup` because it could not be opened.
2025-06-10T12:22:14.578245Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.578550Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.578808Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.579174Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb02\wp_wc_product_meta_lookup.ibd' OS error: 103
2025-06-10T12:22:14.579606Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.579860Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.580344Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb02/wp_wc_product_meta_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.580914Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb02/wp_wc_product_meta_lookup` because it could not be opened.
2025-06-10T12:22:14.581351Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.581684Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.581942Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.582343Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb02\wp_wc_rate_limits.ibd' OS error: 103
2025-06-10T12:22:14.582673Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.582933Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.583378Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb02/wp_wc_rate_limits`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.583938Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb02/wp_wc_rate_limits` because it could not be opened.
2025-06-10T12:22:14.584330Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.584630Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.584899Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.585288Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb02\wp_wc_reserved_stock.ibd' OS error: 103
2025-06-10T12:22:14.585647Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.585907Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.587063Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb02/wp_wc_reserved_stock`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.587936Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb02/wp_wc_reserved_stock` because it could not be opened.
2025-06-10T12:22:14.588710Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.588975Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.589386Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.590178Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb02\wp_wc_tax_rate_classes.ibd' OS error: 103
2025-06-10T12:22:14.590858Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.591156Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.591600Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb02/wp_wc_tax_rate_classes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.592235Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb02/wp_wc_tax_rate_classes` because it could not be opened.
2025-06-10T12:22:14.592794Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.593090Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.593367Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.593858Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb02\wp_wc_webhooks.ibd' OS error: 103
2025-06-10T12:22:14.594194Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.594467Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.594987Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb02/wp_wc_webhooks`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.595569Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb02/wp_wc_webhooks` because it could not be opened.
2025-06-10T12:22:14.596098Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.596421Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.596716Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.597103Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb02\wp_woocommerce_api_keys.ibd' OS error: 103
2025-06-10T12:22:14.597464Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.597863Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.598292Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb02/wp_woocommerce_api_keys`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.598965Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb02/wp_woocommerce_api_keys` because it could not be opened.
2025-06-10T12:22:14.599395Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.599711Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.599993Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.600376Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb02\wp_woocommerce_attribute_taxonomies.ibd' OS error: 103
2025-06-10T12:22:14.600817Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.601080Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.601490Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb02/wp_woocommerce_attribute_taxonomies`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.602154Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb02/wp_woocommerce_attribute_taxonomies` because it could not be opened.
2025-06-10T12:22:14.602774Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.603059Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.603335Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.603778Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb02\wp_woocommerce_downloadable_product_permissions.ibd' OS error: 103
2025-06-10T12:22:14.604173Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.604436Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.604917Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb02/wp_woocommerce_downloadable_product_permissions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.605547Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb02/wp_woocommerce_downloadable_product_permissions` because it could not be opened.
2025-06-10T12:22:14.606062Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.606327Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.606595Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.607038Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb02\wp_woocommerce_log.ibd' OS error: 103
2025-06-10T12:22:14.607367Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.607676Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.608110Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb02/wp_woocommerce_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.608781Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb02/wp_woocommerce_log` because it could not be opened.
2025-06-10T12:22:14.609187Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.609449Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.609786Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.610166Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb02\wp_woocommerce_order_itemmeta.ibd' OS error: 103
2025-06-10T12:22:14.610527Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.610848Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.611263Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb02/wp_woocommerce_order_itemmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.611927Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb02/wp_woocommerce_order_itemmeta` because it could not be opened.
2025-06-10T12:22:14.612368Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.612719Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.613019Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.613405Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb02\wp_woocommerce_order_items.ibd' OS error: 103
2025-06-10T12:22:14.613832Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.614094Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.614498Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb02/wp_woocommerce_order_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.615165Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb02/wp_woocommerce_order_items` because it could not be opened.
2025-06-10T12:22:14.615580Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.615903Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.616172Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.616551Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb02\wp_woocommerce_payment_tokenmeta.ibd' OS error: 103
2025-06-10T12:22:14.616984Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.617246Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.617719Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb02/wp_woocommerce_payment_tokenmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.618673Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb02/wp_woocommerce_payment_tokenmeta` because it could not be opened.
2025-06-10T12:22:14.619086Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.619732Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.620185Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.620572Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb02\wp_woocommerce_payment_tokens.ibd' OS error: 103
2025-06-10T12:22:14.621679Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.621950Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.622559Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb02/wp_woocommerce_payment_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.623271Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb02/wp_woocommerce_payment_tokens` because it could not be opened.
2025-06-10T12:22:14.623852Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.624146Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.624432Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.624800Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb02\wp_woocommerce_sessions.ibd' OS error: 103
2025-06-10T12:22:14.625213Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.625466Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.625863Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb02/wp_woocommerce_sessions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.626577Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb02/wp_woocommerce_sessions` because it could not be opened.
2025-06-10T12:22:14.627208Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.627473Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.627774Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.628260Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb02\wp_woocommerce_shipping_zone_locations.ibd' OS error: 103
2025-06-10T12:22:14.628663Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.629019Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.629537Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb02/wp_woocommerce_shipping_zone_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.630382Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb02/wp_woocommerce_shipping_zone_locations` because it could not be opened.
2025-06-10T12:22:14.630983Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.631267Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.631550Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.631983Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb02\wp_woocommerce_shipping_zone_methods.ibd' OS error: 103
2025-06-10T12:22:14.632359Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.632619Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.633086Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb02/wp_woocommerce_shipping_zone_methods`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.633655Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb02/wp_woocommerce_shipping_zone_methods` because it could not be opened.
2025-06-10T12:22:14.634126Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.634380Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.634632Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.635100Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb02\wp_woocommerce_shipping_zones.ibd' OS error: 103
2025-06-10T12:22:14.635440Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.635686Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.636146Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb02/wp_woocommerce_shipping_zones`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.636710Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb02/wp_woocommerce_shipping_zones` because it could not be opened.
2025-06-10T12:22:14.637206Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.637463Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.637717Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.638217Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb02\wp_woocommerce_tax_rate_locations.ibd' OS error: 103
2025-06-10T12:22:14.638571Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.638815Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.639495Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb02/wp_woocommerce_tax_rate_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.640321Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb02/wp_woocommerce_tax_rate_locations` because it could not be opened.
2025-06-10T12:22:14.640733Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.641033Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.641405Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.641821Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb02\wp_woocommerce_tax_rates.ibd' OS error: 103
2025-06-10T12:22:14.642183Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.642443Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.643046Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb02/wp_woocommerce_tax_rates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.643960Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb02/wp_woocommerce_tax_rates` because it could not be opened.
2025-06-10T12:22:14.644473Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.644809Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.645181Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.645541Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb02\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:14.645896Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.646191Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.646582Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb02/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.647226Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb02/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:14.647617Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.647902Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.648202Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.648570Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb02\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:14.648938Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.649206Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.649781Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb02/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.650512Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb02/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:14.651032Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.651290Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.651553Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.651972Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb02\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:14.652294Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.652540Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.652978Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb02/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.653545Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb02/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:14.654198Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.654490Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.654774Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.655199Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb02\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:14.655555Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.655816Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.656361Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb02/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.656999Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb02/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:14.657728Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.658045Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.658322Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.658705Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb03\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:14.659109Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.659374Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.660015Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb03/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.660609Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb03/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:14.661157Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.661409Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.661875Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.662275Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb03\wp_comments.ibd' OS error: 103
2025-06-10T12:22:14.662777Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.663136Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.663538Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb03/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.664132Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb03/wp_comments` because it could not be opened.
2025-06-10T12:22:14.664546Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.664826Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.665120Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.665488Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb03\wp_links.ibd' OS error: 103
2025-06-10T12:22:14.665802Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.666386Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.667293Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb03/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.668668Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb03/wp_links` because it could not be opened.
2025-06-10T12:22:14.669170Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.669440Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.669771Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.670157Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb03\wp_options.ibd' OS error: 103
2025-06-10T12:22:14.670845Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.671118Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.671564Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb03/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.672252Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb03/wp_options` because it could not be opened.
2025-06-10T12:22:14.672670Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.673031Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.673425Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.673919Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb03\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:14.674331Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.674593Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.675098Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb03/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.675640Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb03/wp_postmeta` because it could not be opened.
2025-06-10T12:22:14.676173Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.676432Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.676690Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.677172Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb03\wp_posts.ibd' OS error: 103
2025-06-10T12:22:14.677472Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.677846Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.678272Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb03/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.678926Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb03/wp_posts` because it could not be opened.
2025-06-10T12:22:14.679323Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.679579Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.679950Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.680315Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb03\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:14.680637Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.680988Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.681378Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb03/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.681991Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb03/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:14.682378Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.682634Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.682981Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.683344Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb03\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:14.683658Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.684202Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.684644Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb03/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.685275Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb03/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:14.685654Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.686140Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.686418Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.686815Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb03\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:14.687133Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.687395Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.687830Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb03/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.688380Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb03/wp_termmeta` because it could not be opened.
2025-06-10T12:22:14.688778Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.689043Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.689315Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.689696Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb03\wp_terms.ibd' OS error: 103
2025-06-10T12:22:14.690257Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.690552Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.690994Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb03/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.691547Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb03/wp_terms` because it could not be opened.
2025-06-10T12:22:14.691963Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.692232Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.692503Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.692968Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb03\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:14.693280Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.693528Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.694016Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb03/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.694601Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb03/wp_usermeta` because it could not be opened.
2025-06-10T12:22:14.695431Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.695745Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.696044Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.696565Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\botiga_sb03\wp_users.ibd' OS error: 103
2025-06-10T12:22:14.697005Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.697251Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.697632Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `botiga_sb03/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.699336Z 0 [Warning] InnoDB: Ignoring tablespace `botiga_sb03/wp_users` because it could not be opened.
2025-06-10T12:22:14.700872Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.701220Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.701527Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.701997Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\builder_elelite\testing1.ibd' OS error: 103
2025-06-10T12:22:14.702391Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.703039Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.703516Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `builder_elelite/testing1`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.704152Z 0 [Warning] InnoDB: Ignoring tablespace `builder_elelite/testing1` because it could not be opened.
2025-06-10T12:22:14.704988Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.705278Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.705553Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.705980Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_actionscheduler_actions.ibd' OS error: 103
2025-06-10T12:22:14.706346Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.706611Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.707068Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_actionscheduler_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.707678Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_actionscheduler_actions` because it could not be opened.
2025-06-10T12:22:14.708200Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.708477Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.708752Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.709196Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_actionscheduler_claims.ibd' OS error: 103
2025-06-10T12:22:14.709571Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.709852Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.710294Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_actionscheduler_claims`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.710931Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_actionscheduler_claims` because it could not be opened.
2025-06-10T12:22:14.711388Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.711653Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.711955Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.712333Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_actionscheduler_groups.ibd' OS error: 103
2025-06-10T12:22:14.712694Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.712981Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.713489Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_actionscheduler_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.714121Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_actionscheduler_groups` because it could not be opened.
2025-06-10T12:22:14.714574Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.714873Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.715151Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.715524Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_actionscheduler_logs.ibd' OS error: 103
2025-06-10T12:22:14.715899Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.716162Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.716575Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_actionscheduler_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.717191Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_actionscheduler_logs` because it could not be opened.
2025-06-10T12:22:14.717601Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.717892Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.718163Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.718538Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:14.718896Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.719157Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.719557Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.720142Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:14.720515Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.720773Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.721071Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.721449Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_comments.ibd' OS error: 103
2025-06-10T12:22:14.721770Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.722063Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.722472Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.723055Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_comments` because it could not be opened.
2025-06-10T12:22:14.723450Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.723713Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.724023Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.724409Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:14.724728Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.725011Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.725419Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.725998Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_fbv` because it could not be opened.
2025-06-10T12:22:14.726380Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.726640Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.726924Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.727305Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:14.727654Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.727943Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.728340Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.728937Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:14.729347Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.729608Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.729904Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.730287Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_links.ibd' OS error: 103
2025-06-10T12:22:14.730635Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.730905Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.731596Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.732189Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_links` because it could not be opened.
2025-06-10T12:22:14.733218Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.733744Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.734049Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.734750Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_options.ibd' OS error: 103
2025-06-10T12:22:14.735137Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.735389Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.735854Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.736462Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_options` because it could not be opened.
2025-06-10T12:22:14.736897Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.737185Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.737532Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.737926Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_post_views.ibd' OS error: 103
2025-06-10T12:22:14.738259Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.738587Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.739003Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_post_views`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.739651Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_post_views` because it could not be opened.
2025-06-10T12:22:14.740134Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.740469Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.740763Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.741147Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:14.741550Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.741824Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.742254Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.742966Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_postmeta` because it could not be opened.
2025-06-10T12:22:14.743400Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.743671Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.743943Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.744325Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_posts.ibd' OS error: 103
2025-06-10T12:22:14.744723Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.744987Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.745441Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.746004Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_posts` because it could not be opened.
2025-06-10T12:22:14.746373Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.746727Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.747029Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.747451Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_redirection_404.ibd' OS error: 103
2025-06-10T12:22:14.747801Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.748067Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.748750Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_redirection_404`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.749341Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_redirection_404` because it could not be opened.
2025-06-10T12:22:14.749792Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.750219Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.750527Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.750913Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_redirection_groups.ibd' OS error: 103
2025-06-10T12:22:14.751307Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.751610Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.752026Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_redirection_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.752638Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_redirection_groups` because it could not be opened.
2025-06-10T12:22:14.753049Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.753315Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.753618Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.754002Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_redirection_items.ibd' OS error: 103
2025-06-10T12:22:14.754350Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.754681Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.755096Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_redirection_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.755756Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_redirection_items` because it could not be opened.
2025-06-10T12:22:14.756224Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.756568Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.756894Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.757301Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_redirection_logs.ibd' OS error: 103
2025-06-10T12:22:14.757746Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.758003Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.758490Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_redirection_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.759092Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_redirection_logs` because it could not be opened.
2025-06-10T12:22:14.759626Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.759941Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.760208Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.760700Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_revslider_css.ibd' OS error: 103
2025-06-10T12:22:14.761025Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.761468Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.762010Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_revslider_css`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.762899Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_revslider_css` because it could not be opened.
2025-06-10T12:22:14.763736Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.764429Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.764703Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.765825Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_revslider_css_bkp.ibd' OS error: 103
2025-06-10T12:22:14.766914Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.767182Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.767680Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_revslider_css_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.768285Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_revslider_css_bkp` because it could not be opened.
2025-06-10T12:22:14.768724Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.768987Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.769321Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.769773Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_revslider_layer_animations.ibd' OS error: 103
2025-06-10T12:22:14.770143Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.770443Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.770853Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_revslider_layer_animations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.771494Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_revslider_layer_animations` because it could not be opened.
2025-06-10T12:22:14.772002Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.772310Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.772587Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.772973Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_revslider_layer_animations_bkp.ibd' OS error: 103
2025-06-10T12:22:14.773394Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.773662Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.774084Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_revslider_layer_animations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.774740Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_revslider_layer_animations_bkp` because it could not be opened.
2025-06-10T12:22:14.775262Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.775534Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.775913Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.776343Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_revslider_navigations.ibd' OS error: 103
2025-06-10T12:22:14.776701Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.776999Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.777493Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_revslider_navigations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.778129Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_revslider_navigations` because it could not be opened.
2025-06-10T12:22:14.778606Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.778874Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.779150Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.779649Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_revslider_navigations_bkp.ibd' OS error: 103
2025-06-10T12:22:14.780021Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.780321Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.780760Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_revslider_navigations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.781392Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_revslider_navigations_bkp` because it could not be opened.
2025-06-10T12:22:14.781961Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.782266Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.782540Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.782925Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_revslider_sliders.ibd' OS error: 103
2025-06-10T12:22:14.783305Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.783567Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.783981Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_revslider_sliders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.784591Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_revslider_sliders` because it could not be opened.
2025-06-10T12:22:14.784991Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.785281Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.785553Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.785936Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_revslider_sliders_bkp.ibd' OS error: 103
2025-06-10T12:22:14.786358Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.786758Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.787421Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_revslider_sliders_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.788363Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_revslider_sliders_bkp` because it could not be opened.
2025-06-10T12:22:14.788989Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.789418Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.789857Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.790281Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_revslider_slides.ibd' OS error: 103
2025-06-10T12:22:14.790632Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.790895Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.791354Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_revslider_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.791940Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_revslider_slides` because it could not be opened.
2025-06-10T12:22:14.792385Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.792649Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.792918Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.793333Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_revslider_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:14.793692Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.794039Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.794540Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_revslider_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.795112Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_revslider_slides_bkp` because it could not be opened.
2025-06-10T12:22:14.796097Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.796385Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.796765Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.797538Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_revslider_static_slides.ibd' OS error: 103
2025-06-10T12:22:14.798931Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.799611Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.800129Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_revslider_static_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.800882Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_revslider_static_slides` because it could not be opened.
2025-06-10T12:22:14.801410Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.801677Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.801949Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.802399Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_revslider_static_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:14.802768Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.803095Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.803548Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_revslider_static_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.804263Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_revslider_static_slides_bkp` because it could not be opened.
2025-06-10T12:22:14.804769Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.805087Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.805435Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.805856Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_sbi_instagram_feed_locator.ibd' OS error: 103
2025-06-10T12:22:14.806314Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.806591Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.807100Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_sbi_instagram_feed_locator`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.807971Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_sbi_instagram_feed_locator` because it could not be opened.
2025-06-10T12:22:14.808491Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.808765Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.809108Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.809491Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_sbi_instagram_feeds_posts.ibd' OS error: 103
2025-06-10T12:22:14.809853Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.810187Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.810600Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_sbi_instagram_feeds_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.811263Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_sbi_instagram_feeds_posts` because it could not be opened.
2025-06-10T12:22:14.811700Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.812010Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.812296Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.812672Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_sbi_instagram_posts.ibd' OS error: 103
2025-06-10T12:22:14.813090Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.813352Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.813769Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_sbi_instagram_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.814537Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_sbi_instagram_posts` because it could not be opened.
2025-06-10T12:22:14.814941Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.815326Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.815585Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.815950Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:14.816469Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.816774Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.817214Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.817942Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:14.818440Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.818705Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.819037Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.819475Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:14.819830Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.820136Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.820539Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.821217Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:14.821633Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.821886Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.822231Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.822601Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:14.822985Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.823254Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.823649Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.824250Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_termmeta` because it could not be opened.
2025-06-10T12:22:14.824617Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.824872Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.825198Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.825567Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_terms.ibd' OS error: 103
2025-06-10T12:22:14.825873Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.826180Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.826793Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.827817Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_terms` because it could not be opened.
2025-06-10T12:22:14.828351Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.828901Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.829160Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.830776Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:14.831248Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.831520Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.831979Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.832585Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_usermeta` because it could not be opened.
2025-06-10T12:22:14.833009Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.833277Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.833549Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.833985Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_users.ibd' OS error: 103
2025-06-10T12:22:14.834307Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.834574Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.835046Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.835658Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_users` because it could not be opened.
2025-06-10T12:22:14.836106Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.836384Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.836733Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.837191Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_wc_admin_note_actions.ibd' OS error: 103
2025-06-10T12:22:14.837630Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.837915Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.838312Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_wc_admin_note_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.839125Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_wc_admin_note_actions` because it could not be opened.
2025-06-10T12:22:14.839693Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.839960Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.840217Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.840657Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_wc_admin_notes.ibd' OS error: 103
2025-06-10T12:22:14.840996Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.841314Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.841828Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_wc_admin_notes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.842439Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_wc_admin_notes` because it could not be opened.
2025-06-10T12:22:14.842919Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.843180Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.843445Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.843892Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_wc_category_lookup.ibd' OS error: 103
2025-06-10T12:22:14.844292Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.844573Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.844989Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_wc_category_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.845638Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_wc_category_lookup` because it could not be opened.
2025-06-10T12:22:14.846040Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.846302Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.846618Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.847027Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_wc_customer_lookup.ibd' OS error: 103
2025-06-10T12:22:14.847384Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.847694Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.848130Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_wc_customer_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.848752Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_wc_customer_lookup` because it could not be opened.
2025-06-10T12:22:14.849174Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.849446Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.849763Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.850158Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_wc_download_log.ibd' OS error: 103
2025-06-10T12:22:14.850489Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.850948Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.851370Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_wc_download_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.852077Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_wc_download_log` because it could not be opened.
2025-06-10T12:22:14.852578Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.853303Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.853723Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.854212Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_wc_order_coupon_lookup.ibd' OS error: 103
2025-06-10T12:22:14.854626Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.854898Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.855496Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_wc_order_coupon_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.856110Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_wc_order_coupon_lookup` because it could not be opened.
2025-06-10T12:22:14.856632Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.856903Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.857177Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.857647Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_wc_order_product_lookup.ibd' OS error: 103
2025-06-10T12:22:14.858235Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.858556Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.859037Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_wc_order_product_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.859676Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_wc_order_product_lookup` because it could not be opened.
2025-06-10T12:22:14.860231Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.860510Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.860886Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.861504Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_wc_order_stats.ibd' OS error: 103
2025-06-10T12:22:14.861847Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.862600Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.863210Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_wc_order_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.864145Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_wc_order_stats` because it could not be opened.
2025-06-10T12:22:14.864694Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.864996Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.865274Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.865847Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_wc_order_tax_lookup.ibd' OS error: 103
2025-06-10T12:22:14.866499Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.866833Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.867246Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_wc_order_tax_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.867938Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_wc_order_tax_lookup` because it could not be opened.
2025-06-10T12:22:14.868432Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.868776Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.869065Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.869470Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_wc_product_meta_lookup.ibd' OS error: 103
2025-06-10T12:22:14.869957Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.870276Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.870970Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_wc_product_meta_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.871842Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_wc_product_meta_lookup` because it could not be opened.
2025-06-10T12:22:14.872325Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.872645Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.872999Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.873380Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_wc_reserved_stock.ibd' OS error: 103
2025-06-10T12:22:14.873858Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.874138Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.874528Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_wc_reserved_stock`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.875185Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_wc_reserved_stock` because it could not be opened.
2025-06-10T12:22:14.875599Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.875968Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.876235Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.876595Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_wc_tax_rate_classes.ibd' OS error: 103
2025-06-10T12:22:14.877086Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.877330Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.877798Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_wc_tax_rate_classes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.878336Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_wc_tax_rate_classes` because it could not be opened.
2025-06-10T12:22:14.878812Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.879092Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.879344Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.879886Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_wc_webhooks.ibd' OS error: 103
2025-06-10T12:22:14.880280Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.880535Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.881005Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_wc_webhooks`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.881600Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_wc_webhooks` because it could not be opened.
2025-06-10T12:22:14.882250Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.882511Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.882909Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.883323Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_woocommerce_api_keys.ibd' OS error: 103
2025-06-10T12:22:14.883762Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.884033Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.884643Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_woocommerce_api_keys`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.885266Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_woocommerce_api_keys` because it could not be opened.
2025-06-10T12:22:14.885761Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.886163Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.886454Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.886957Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_woocommerce_attribute_taxonomies.ibd' OS error: 103
2025-06-10T12:22:14.887473Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.887801Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.888203Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_woocommerce_attribute_taxonomies`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.888848Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_woocommerce_attribute_taxonomies` because it could not be opened.
2025-06-10T12:22:14.889405Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.889708Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.889983Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.890348Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_woocommerce_downloadable_product_permissions.ibd' OS error: 103
2025-06-10T12:22:14.890818Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.891082Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.891474Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_woocommerce_downloadable_product_permissions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.892181Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_woocommerce_downloadable_product_permissions` because it could not be opened.
2025-06-10T12:22:14.892692Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.892979Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.893231Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.893589Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_woocommerce_log.ibd' OS error: 103
2025-06-10T12:22:14.894037Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.894290Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.894820Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_woocommerce_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.895384Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_woocommerce_log` because it could not be opened.
2025-06-10T12:22:14.895907Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.896153Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.896403Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.896874Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_woocommerce_order_itemmeta.ibd' OS error: 103
2025-06-10T12:22:14.897323Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.897687Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.898188Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_woocommerce_order_itemmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.898918Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_woocommerce_order_itemmeta` because it could not be opened.
2025-06-10T12:22:14.899468Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.899871Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.900171Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.900562Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_woocommerce_order_items.ibd' OS error: 103
2025-06-10T12:22:14.901218Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.901554Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.902070Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_woocommerce_order_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.902770Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_woocommerce_order_items` because it could not be opened.
2025-06-10T12:22:14.903405Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.903716Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.904058Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.904409Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_woocommerce_payment_tokenmeta.ibd' OS error: 103
2025-06-10T12:22:14.904872Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.905179Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.905560Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_woocommerce_payment_tokenmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.906293Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_woocommerce_payment_tokenmeta` because it could not be opened.
2025-06-10T12:22:14.906848Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.907121Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.907458Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.909977Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_woocommerce_payment_tokens.ibd' OS error: 103
2025-06-10T12:22:14.910926Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.911723Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.912160Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_woocommerce_payment_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.912894Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_woocommerce_payment_tokens` because it could not be opened.
2025-06-10T12:22:14.913382Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.913688Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.913957Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.914334Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_woocommerce_sessions.ibd' OS error: 103
2025-06-10T12:22:14.914753Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.915076Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.915498Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_woocommerce_sessions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.916158Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_woocommerce_sessions` because it could not be opened.
2025-06-10T12:22:14.916661Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.916941Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.917213Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.917645Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_woocommerce_shipping_zone_locations.ibd' OS error: 103
2025-06-10T12:22:14.918033Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.918351Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.918871Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_woocommerce_shipping_zone_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.919572Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_woocommerce_shipping_zone_locations` because it could not be opened.
2025-06-10T12:22:14.920425Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.920719Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.920993Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.921375Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_woocommerce_shipping_zone_methods.ibd' OS error: 103
2025-06-10T12:22:14.921798Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.922059Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.922467Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_woocommerce_shipping_zone_methods`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.923150Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_woocommerce_shipping_zone_methods` because it could not be opened.
2025-06-10T12:22:14.923806Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.924074Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.924332Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.924887Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_woocommerce_shipping_zones.ibd' OS error: 103
2025-06-10T12:22:14.925264Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.925574Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.926026Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_woocommerce_shipping_zones`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.926714Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_woocommerce_shipping_zones` because it could not be opened.
2025-06-10T12:22:14.927154Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.927409Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.927736Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.928099Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_woocommerce_tax_rate_locations.ibd' OS error: 103
2025-06-10T12:22:14.928452Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.928765Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.929170Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_woocommerce_tax_rate_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.929891Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_woocommerce_tax_rate_locations` because it could not be opened.
2025-06-10T12:22:14.930403Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.930737Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.931303Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.931741Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_woocommerce_tax_rates.ibd' OS error: 103
2025-06-10T12:22:14.932274Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.932658Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.933195Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_woocommerce_tax_rates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.933914Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_woocommerce_tax_rates` because it could not be opened.
2025-06-10T12:22:14.934365Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.934845Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.935123Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.935535Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:14.935956Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.936334Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.936821Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.937383Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:14.937988Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.938242Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.938576Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.940427Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:14.940760Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.941348Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.942020Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.942858Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:14.943698Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.943996Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.944307Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.944740Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:14.945120Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.945383Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.945850Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.946445Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:14.946987Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.947244Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.947622Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.948122Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech1\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:14.948592Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.948847Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.949246Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech1/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.950014Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech1/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:14.951104Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.951561Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.952020Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.952500Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_actionscheduler_actions.ibd' OS error: 103
2025-06-10T12:22:14.952886Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.953171Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.953702Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_actionscheduler_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.954435Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_actionscheduler_actions` because it could not be opened.
2025-06-10T12:22:14.954915Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.955196Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.955690Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.956067Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_actionscheduler_claims.ibd' OS error: 103
2025-06-10T12:22:14.956479Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.956750Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.957144Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_actionscheduler_claims`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.957932Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_actionscheduler_claims` because it could not be opened.
2025-06-10T12:22:14.958494Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.958836Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.959139Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.959555Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_actionscheduler_groups.ibd' OS error: 103
2025-06-10T12:22:14.959897Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.960151Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.960694Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_actionscheduler_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.961605Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_actionscheduler_groups` because it could not be opened.
2025-06-10T12:22:14.962085Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.962418Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.962740Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.963094Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_actionscheduler_logs.ibd' OS error: 103
2025-06-10T12:22:14.963531Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.963780Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.964218Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_actionscheduler_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.964888Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_actionscheduler_logs` because it could not be opened.
2025-06-10T12:22:14.965464Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.965753Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.966041Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.966551Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:14.966865Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.967116Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.967903Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.968520Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:14.968920Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.969175Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.969559Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.970170Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_comments.ibd' OS error: 103
2025-06-10T12:22:14.970530Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.970916Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.971461Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.972191Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_comments` because it could not be opened.
2025-06-10T12:22:14.972992Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.973707Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.973975Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.974450Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:14.974850Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.975130Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.975561Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.976140Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_fbv` because it could not be opened.
2025-06-10T12:22:14.976543Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.976834Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.977109Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.977494Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:14.977899Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.978162Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.978582Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.979341Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:14.979939Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.980272Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.980590Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.981051Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_links.ibd' OS error: 103
2025-06-10T12:22:14.981390Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.981698Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.982120Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.982754Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_links` because it could not be opened.
2025-06-10T12:22:14.983204Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.983459Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.983786Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.984147Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_options.ibd' OS error: 103
2025-06-10T12:22:14.984457Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.984754Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.985163Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.985762Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_options` because it could not be opened.
2025-06-10T12:22:14.986159Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.986410Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.986730Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.987091Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_post_views.ibd' OS error: 103
2025-06-10T12:22:14.987404Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.987697Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.988162Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_post_views`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.988772Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_post_views` because it could not be opened.
2025-06-10T12:22:14.989229Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.989497Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.989827Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.990195Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:14.990520Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.990869Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.991263Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.991877Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_postmeta` because it could not be opened.
2025-06-10T12:22:14.992243Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.992497Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.992821Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.993187Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_posts.ibd' OS error: 103
2025-06-10T12:22:14.993499Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.993844Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.994243Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.994846Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_posts` because it could not be opened.
2025-06-10T12:22:14.995214Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.995471Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.995823Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.996225Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_redirection_404.ibd' OS error: 103
2025-06-10T12:22:14.996578Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.996947Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:14.997361Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_redirection_404`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:14.997990Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_redirection_404` because it could not be opened.
2025-06-10T12:22:14.998385Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:14.998696Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:14.998969Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:14.999335Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_redirection_groups.ibd' OS error: 103
2025-06-10T12:22:14.999732Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:14.999984Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.000386Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_redirection_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.001126Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_redirection_groups` because it could not be opened.
2025-06-10T12:22:15.001622Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.001900Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.002170Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.003351Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_redirection_items.ibd' OS error: 103
2025-06-10T12:22:15.004488Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.004994Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.005540Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_redirection_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.006643Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_redirection_items` because it could not be opened.
2025-06-10T12:22:15.007199Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.007504Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.007862Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.008276Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_redirection_logs.ibd' OS error: 103
2025-06-10T12:22:15.008648Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.008987Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.009454Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_redirection_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.010240Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_redirection_logs` because it could not be opened.
2025-06-10T12:22:15.010741Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.011076Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.011339Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.011707Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_revslider_css.ibd' OS error: 103
2025-06-10T12:22:15.012113Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.012368Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.012793Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_revslider_css`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.013455Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_revslider_css` because it could not be opened.
2025-06-10T12:22:15.014080Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.014372Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.014655Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.015113Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_revslider_css_bkp.ibd' OS error: 103
2025-06-10T12:22:15.015469Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.015717Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.016209Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_revslider_css_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.016801Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_revslider_css_bkp` because it could not be opened.
2025-06-10T12:22:15.017335Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.017613Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.018003Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.018369Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_revslider_layer_animations.ibd' OS error: 103
2025-06-10T12:22:15.018721Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.019043Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.019436Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_revslider_layer_animations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.020083Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_revslider_layer_animations` because it could not be opened.
2025-06-10T12:22:15.020487Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.020964Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.021232Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.021601Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_revslider_layer_animations_bkp.ibd' OS error: 103
2025-06-10T12:22:15.022132Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.022412Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.022866Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_revslider_layer_animations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.023460Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_revslider_layer_animations_bkp` because it could not be opened.
2025-06-10T12:22:15.024007Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.024278Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.024538Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.025070Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_revslider_navigations.ibd' OS error: 103
2025-06-10T12:22:15.025411Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.025700Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.026217Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_revslider_navigations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.026868Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_revslider_navigations` because it could not be opened.
2025-06-10T12:22:15.027307Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.027553Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.027892Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.028400Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_revslider_navigations_bkp.ibd' OS error: 103
2025-06-10T12:22:15.028934Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.029283Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.029946Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_revslider_navigations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.030668Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_revslider_navigations_bkp` because it could not be opened.
2025-06-10T12:22:15.031167Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.031431Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.031714Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.032199Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_revslider_sliders.ibd' OS error: 103
2025-06-10T12:22:15.032549Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.032845Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.033254Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_revslider_sliders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.033976Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_revslider_sliders` because it could not be opened.
2025-06-10T12:22:15.034394Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.034710Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.035353Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.035941Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_revslider_sliders_bkp.ibd' OS error: 103
2025-06-10T12:22:15.037779Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.038977Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.039460Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_revslider_sliders_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.040159Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_revslider_sliders_bkp` because it could not be opened.
2025-06-10T12:22:15.040706Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.040989Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.041261Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.041684Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_revslider_slides.ibd' OS error: 103
2025-06-10T12:22:15.042030Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.042292Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.042841Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_revslider_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.043473Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_revslider_slides` because it could not be opened.
2025-06-10T12:22:15.043949Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.044232Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.044541Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.044979Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_revslider_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:15.045339Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.045635Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.046057Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_revslider_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.046702Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_revslider_slides_bkp` because it could not be opened.
2025-06-10T12:22:15.047240Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.047547Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.047826Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.048212Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_revslider_static_slides.ibd' OS error: 103
2025-06-10T12:22:15.048610Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.048874Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.049293Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_revslider_static_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.049923Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_revslider_static_slides` because it could not be opened.
2025-06-10T12:22:15.050359Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.050697Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.050976Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.051369Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_revslider_static_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:15.051757Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.052016Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.052470Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_revslider_static_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.053103Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_revslider_static_slides_bkp` because it could not be opened.
2025-06-10T12:22:15.053540Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.053810Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.054082Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.054502Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_sbi_instagram_feed_locator.ibd' OS error: 103
2025-06-10T12:22:15.054877Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.055143Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.055702Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_sbi_instagram_feed_locator`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.056309Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_sbi_instagram_feed_locator` because it could not be opened.
2025-06-10T12:22:15.056801Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.057066Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.057352Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.057750Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_sbi_instagram_feeds_posts.ibd' OS error: 103
2025-06-10T12:22:15.058116Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.058407Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.058820Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_sbi_instagram_feeds_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.059448Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_sbi_instagram_feeds_posts` because it could not be opened.
2025-06-10T12:22:15.059928Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.060213Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.060505Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.060882Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_sbi_instagram_posts.ibd' OS error: 103
2025-06-10T12:22:15.061229Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.061522Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.061926Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_sbi_instagram_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.062558Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_sbi_instagram_posts` because it could not be opened.
2025-06-10T12:22:15.062975Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.063239Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.063535Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.063922Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:15.064265Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.064550Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.064960Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.065558Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:15.066000Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.066265Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.066580Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.066957Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:15.067435Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.067707Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.068930Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.069823Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:15.070812Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.071130Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.071408Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.071810Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:15.072163Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.072429Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.072858Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.073419Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_termmeta` because it could not be opened.
2025-06-10T12:22:15.073874Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.074141Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.074415Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.074820Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_terms.ibd' OS error: 103
2025-06-10T12:22:15.075144Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.075410Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.076074Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.076722Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_terms` because it could not be opened.
2025-06-10T12:22:15.077197Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.077467Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.077783Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.078176Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:15.078542Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.078812Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.079224Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.079816Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_usermeta` because it could not be opened.
2025-06-10T12:22:15.080191Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.080454Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.080755Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.081141Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_users.ibd' OS error: 103
2025-06-10T12:22:15.081471Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.081750Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.082163Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.082871Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_users` because it could not be opened.
2025-06-10T12:22:15.083282Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.083584Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.083856Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.084241Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_wc_admin_note_actions.ibd' OS error: 103
2025-06-10T12:22:15.084638Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.084902Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.085309Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_wc_admin_note_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.086089Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_wc_admin_note_actions` because it could not be opened.
2025-06-10T12:22:15.086529Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.086797Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.087066Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.087461Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_wc_admin_notes.ibd' OS error: 103
2025-06-10T12:22:15.087819Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.088081Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.088518Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_wc_admin_notes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.089103Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_wc_admin_notes` because it could not be opened.
2025-06-10T12:22:15.089510Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.089790Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.090079Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.090476Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_wc_category_lookup.ibd' OS error: 103
2025-06-10T12:22:15.090829Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.091090Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.091533Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_wc_category_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.092122Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_wc_category_lookup` because it could not be opened.
2025-06-10T12:22:15.092551Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.092818Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.093084Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.093492Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_wc_customer_lookup.ibd' OS error: 103
2025-06-10T12:22:15.093846Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.094109Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.094723Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_wc_customer_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.095347Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_wc_customer_lookup` because it could not be opened.
2025-06-10T12:22:15.095811Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.096084Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.096354Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.096786Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_wc_download_log.ibd' OS error: 103
2025-06-10T12:22:15.097133Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.097392Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.097837Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_wc_download_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.098434Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_wc_download_log` because it could not be opened.
2025-06-10T12:22:15.098847Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.099112Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.099378Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.099787Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_wc_order_coupon_lookup.ibd' OS error: 103
2025-06-10T12:22:15.100147Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.100412Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.100849Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_wc_order_coupon_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.101458Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_wc_order_coupon_lookup` because it could not be opened.
2025-06-10T12:22:15.101878Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.102142Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.102410Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.102818Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_wc_order_product_lookup.ibd' OS error: 103
2025-06-10T12:22:15.103175Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.103449Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.103879Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_wc_order_product_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.104499Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_wc_order_product_lookup` because it could not be opened.
2025-06-10T12:22:15.104907Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.105170Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.105502Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.105960Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_wc_order_stats.ibd' OS error: 103
2025-06-10T12:22:15.106294Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.106599Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.107015Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_wc_order_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.107667Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_wc_order_stats` because it could not be opened.
2025-06-10T12:22:15.108216Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.108654Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.108941Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.109342Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_wc_order_tax_lookup.ibd' OS error: 103
2025-06-10T12:22:15.109786Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.110084Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.110575Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_wc_order_tax_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.111140Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_wc_order_tax_lookup` because it could not be opened.
2025-06-10T12:22:15.111616Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.111874Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.112138Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.112615Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_wc_product_meta_lookup.ibd' OS error: 103
2025-06-10T12:22:15.112965Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.113264Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.113760Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_wc_product_meta_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.114918Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_wc_product_meta_lookup` because it could not be opened.
2025-06-10T12:22:15.116115Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.116990Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.117910Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.118501Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_wc_reserved_stock.ibd' OS error: 103
2025-06-10T12:22:15.119023Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.119289Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.119729Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_wc_reserved_stock`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.120337Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_wc_reserved_stock` because it could not be opened.
2025-06-10T12:22:15.120798Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.121065Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.121335Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.121789Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_wc_tax_rate_classes.ibd' OS error: 103
2025-06-10T12:22:15.122139Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.122579Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.123153Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_wc_tax_rate_classes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.123884Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_wc_tax_rate_classes` because it could not be opened.
2025-06-10T12:22:15.124343Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.124684Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.124961Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.125338Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_wc_webhooks.ibd' OS error: 103
2025-06-10T12:22:15.125786Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.126037Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.126437Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_wc_webhooks`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.127203Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_wc_webhooks` because it could not be opened.
2025-06-10T12:22:15.127695Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.127956Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.128216Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.128708Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_woocommerce_api_keys.ibd' OS error: 103
2025-06-10T12:22:15.129102Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.129414Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.129848Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_woocommerce_api_keys`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.130444Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_woocommerce_api_keys` because it could not be opened.
2025-06-10T12:22:15.130903Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.131169Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.131443Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.131859Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_woocommerce_attribute_taxonomies.ibd' OS error: 103
2025-06-10T12:22:15.132243Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.132528Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.132949Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_woocommerce_attribute_taxonomies`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.133596Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_woocommerce_attribute_taxonomies` because it could not be opened.
2025-06-10T12:22:15.134025Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.134291Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.134589Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.134982Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_woocommerce_downloadable_product_permissions.ibd' OS error: 103
2025-06-10T12:22:15.135439Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.135767Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.136190Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_woocommerce_downloadable_product_permissions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.136948Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_woocommerce_downloadable_product_permissions` because it could not be opened.
2025-06-10T12:22:15.137429Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.137779Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.138039Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.138408Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_woocommerce_log.ibd' OS error: 103
2025-06-10T12:22:15.138795Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.139085Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.139483Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_woocommerce_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.140142Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_woocommerce_log` because it could not be opened.
2025-06-10T12:22:15.140615Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.140892Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.141187Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.141670Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_woocommerce_order_itemmeta.ibd' OS error: 103
2025-06-10T12:22:15.142055Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.142302Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.142803Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_woocommerce_order_itemmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.143376Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_woocommerce_order_itemmeta` because it could not be opened.
2025-06-10T12:22:15.143872Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.144124Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.144379Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.144796Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_woocommerce_order_items.ibd' OS error: 103
2025-06-10T12:22:15.145160Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.145421Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.145905Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_woocommerce_order_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.146752Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_woocommerce_order_items` because it could not be opened.
2025-06-10T12:22:15.147170Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.147953Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.148259Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.149137Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_woocommerce_payment_tokenmeta.ibd' OS error: 103
2025-06-10T12:22:15.149741Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.150016Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.150519Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_woocommerce_payment_tokenmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.151195Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_woocommerce_payment_tokenmeta` because it could not be opened.
2025-06-10T12:22:15.151765Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.152091Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.152362Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.152746Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_woocommerce_payment_tokens.ibd' OS error: 103
2025-06-10T12:22:15.153163Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.153426Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.153831Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_woocommerce_payment_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.154482Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_woocommerce_payment_tokens` because it could not be opened.
2025-06-10T12:22:15.155009Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.155290Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.155561Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.155992Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_woocommerce_sessions.ibd' OS error: 103
2025-06-10T12:22:15.156347Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.156610Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.157083Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_woocommerce_sessions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.157696Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_woocommerce_sessions` because it could not be opened.
2025-06-10T12:22:15.158253Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.158534Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.158840Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.159260Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_woocommerce_shipping_zone_locations.ibd' OS error: 103
2025-06-10T12:22:15.159673Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.159978Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.160475Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_woocommerce_shipping_zone_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.161150Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_woocommerce_shipping_zone_locations` because it could not be opened.
2025-06-10T12:22:15.161694Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.162004Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.162273Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.162653Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_woocommerce_shipping_zone_methods.ibd' OS error: 103
2025-06-10T12:22:15.163081Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.163346Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.163750Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_woocommerce_shipping_zone_methods`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.164405Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_woocommerce_shipping_zone_methods` because it could not be opened.
2025-06-10T12:22:15.164841Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.165141Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.165406Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.165789Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_woocommerce_shipping_zones.ibd' OS error: 103
2025-06-10T12:22:15.166194Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.166452Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.166876Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_woocommerce_shipping_zones`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.167499Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_woocommerce_shipping_zones` because it could not be opened.
2025-06-10T12:22:15.168051Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.168321Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.168584Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.169001Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_woocommerce_tax_rate_locations.ibd' OS error: 103
2025-06-10T12:22:15.169379Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.169626Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.170080Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_woocommerce_tax_rate_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.170932Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_woocommerce_tax_rate_locations` because it could not be opened.
2025-06-10T12:22:15.171420Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.171689Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.171997Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.172383Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_woocommerce_tax_rates.ibd' OS error: 103
2025-06-10T12:22:15.172743Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.173041Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.173468Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_woocommerce_tax_rates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.174105Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_woocommerce_tax_rates` because it could not be opened.
2025-06-10T12:22:15.174538Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.174805Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.175103Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.175488Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:15.175843Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.176129Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.176566Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.177222Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:15.177659Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.177962Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.178237Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.178620Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:15.179026Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.179295Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.179875Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.180597Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:15.181645Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.181925Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.182602Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.183528Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:15.183892Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.184189Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.184601Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.185207Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:15.185633Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.185900Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.186219Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.186606Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech2\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:15.186991Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.187260Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.187679Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech2/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.188328Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech2/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:15.189285Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.189574Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.189852Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.190276Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_actionscheduler_actions.ibd' OS error: 103
2025-06-10T12:22:15.190663Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.190940Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.191401Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_actionscheduler_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.192032Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_actionscheduler_actions` because it could not be opened.
2025-06-10T12:22:15.192753Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.193061Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.193334Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.193716Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_actionscheduler_claims.ibd' OS error: 103
2025-06-10T12:22:15.194139Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.194455Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.194874Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_actionscheduler_claims`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.195512Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_actionscheduler_claims` because it could not be opened.
2025-06-10T12:22:15.195954Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.196236Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.196507Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.196888Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_actionscheduler_groups.ibd' OS error: 103
2025-06-10T12:22:15.197272Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.197532Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.197969Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_actionscheduler_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.198566Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_actionscheduler_groups` because it could not be opened.
2025-06-10T12:22:15.199000Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.199268Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.199538Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.199932Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_actionscheduler_logs.ibd' OS error: 103
2025-06-10T12:22:15.200302Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.200563Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.201008Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_actionscheduler_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.201604Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_actionscheduler_logs` because it could not be opened.
2025-06-10T12:22:15.202065Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.202333Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.202603Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.203019Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:15.203355Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.203616Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.204087Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.204698Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:15.205225Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.205493Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.205762Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.206178Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_comments.ibd' OS error: 103
2025-06-10T12:22:15.206506Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.206767Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.207206Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.207779Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_comments` because it could not be opened.
2025-06-10T12:22:15.208200Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.208464Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.208733Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.209148Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:15.209466Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.209727Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.210187Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.210771Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_fbv` because it could not be opened.
2025-06-10T12:22:15.211346Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.211908Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.212180Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.212618Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:15.213078Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.213332Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.213999Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.215521Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:15.216379Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.216740Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.217023Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.217411Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_itsec_bans.ibd' OS error: 103
2025-06-10T12:22:15.217857Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.218139Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.218537Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_itsec_bans`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.219174Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_itsec_bans` because it could not be opened.
2025-06-10T12:22:15.219620Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.220021Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.220281Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.220783Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_itsec_dashboard_events.ibd' OS error: 103
2025-06-10T12:22:15.221289Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.221561Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.222080Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_itsec_dashboard_events`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.222778Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_itsec_dashboard_events` because it could not be opened.
2025-06-10T12:22:15.223271Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.223609Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.224045Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.224409Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_itsec_distributed_storage.ibd' OS error: 103
2025-06-10T12:22:15.224867Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.225116Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.225508Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_itsec_distributed_storage`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.226201Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_itsec_distributed_storage` because it could not be opened.
2025-06-10T12:22:15.226704Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.227011Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.227269Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.227741Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_itsec_fingerprints.ibd' OS error: 103
2025-06-10T12:22:15.228150Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.228433Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.228907Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_itsec_fingerprints`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.229497Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_itsec_fingerprints` because it could not be opened.
2025-06-10T12:22:15.229973Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.230235Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.230503Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.230953Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_itsec_geolocation_cache.ibd' OS error: 103
2025-06-10T12:22:15.231313Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.231571Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.232035Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_itsec_geolocation_cache`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.232684Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_itsec_geolocation_cache` because it could not be opened.
2025-06-10T12:22:15.233096Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.233357Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.233751Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.234176Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_itsec_lockouts.ibd' OS error: 103
2025-06-10T12:22:15.234527Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.234861Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.235282Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_itsec_lockouts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.235968Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_itsec_lockouts` because it could not be opened.
2025-06-10T12:22:15.236389Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.236743Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.237027Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.237417Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_itsec_logs.ibd' OS error: 103
2025-06-10T12:22:15.237807Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.238068Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.238478Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_itsec_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.239122Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_itsec_logs` because it could not be opened.
2025-06-10T12:22:15.239569Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.239936Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.240266Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.240695Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_itsec_mutexes.ibd' OS error: 103
2025-06-10T12:22:15.241075Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.241370Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.241854Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_itsec_mutexes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.242778Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_itsec_mutexes` because it could not be opened.
2025-06-10T12:22:15.243331Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.243990Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.244254Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.244970Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_itsec_opaque_tokens.ibd' OS error: 103
2025-06-10T12:22:15.245414Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.245684Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.246191Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_itsec_opaque_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.246877Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_itsec_opaque_tokens` because it could not be opened.
2025-06-10T12:22:15.247327Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.247670Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.247966Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.248459Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_itsec_temp.ibd' OS error: 103
2025-06-10T12:22:15.248845Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.249125Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.249586Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_itsec_temp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.250168Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_itsec_temp` because it could not be opened.
2025-06-10T12:22:15.250679Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.250980Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.251256Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.251672Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_itsec_user_groups.ibd' OS error: 103
2025-06-10T12:22:15.252026Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.252378Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.252843Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_itsec_user_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.253491Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_itsec_user_groups` because it could not be opened.
2025-06-10T12:22:15.253981Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.254257Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.254601Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.255051Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_links.ibd' OS error: 103
2025-06-10T12:22:15.255423Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.255686Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.256094Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.256678Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_links` because it could not be opened.
2025-06-10T12:22:15.257070Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.257348Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.257640Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.258022Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_options.ibd' OS error: 103
2025-06-10T12:22:15.258364Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.258646Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.259067Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.259657Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_options` because it could not be opened.
2025-06-10T12:22:15.260045Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.260308Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.260608Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.261118Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_post_views.ibd' OS error: 103
2025-06-10T12:22:15.261515Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.261773Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.262172Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_post_views`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.263009Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_post_views` because it could not be opened.
2025-06-10T12:22:15.263509Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.263766Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.264049Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.264470Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:15.264796Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.265065Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.265534Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.266100Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_postmeta` because it could not be opened.
2025-06-10T12:22:15.266535Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.266800Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.267071Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.267553Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_posts.ibd' OS error: 103
2025-06-10T12:22:15.267912Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.268205Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.268644Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.269206Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_posts` because it could not be opened.
2025-06-10T12:22:15.269739Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.270010Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.270281Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.270706Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_revslider_css.ibd' OS error: 103
2025-06-10T12:22:15.271048Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.271330Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.271765Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_revslider_css`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.272369Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_revslider_css` because it could not be opened.
2025-06-10T12:22:15.272789Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.273055Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.273344Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.273739Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_revslider_css_bkp.ibd' OS error: 103
2025-06-10T12:22:15.274238Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.274641Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.275046Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_revslider_css_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.275730Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_revslider_css_bkp` because it could not be opened.
2025-06-10T12:22:15.276353Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.276671Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.276932Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.277386Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_revslider_layer_animations.ibd' OS error: 103
2025-06-10T12:22:15.277758Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.278065Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.278724Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_revslider_layer_animations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.279502Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_revslider_layer_animations` because it could not be opened.
2025-06-10T12:22:15.280121Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.280687Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.281390Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.281772Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_revslider_layer_animations_bkp.ibd' OS error: 103
2025-06-10T12:22:15.282358Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.282620Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.283727Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_revslider_layer_animations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.284406Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_revslider_layer_animations_bkp` because it could not be opened.
2025-06-10T12:22:15.284888Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.285152Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.285440Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.285820Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_revslider_navigations.ibd' OS error: 103
2025-06-10T12:22:15.286179Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.286468Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.286878Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_revslider_navigations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.287512Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_revslider_navigations` because it could not be opened.
2025-06-10T12:22:15.287975Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.288248Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.288560Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.289057Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_revslider_navigations_bkp.ibd' OS error: 103
2025-06-10T12:22:15.289484Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.289766Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.290201Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_revslider_navigations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.291118Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_revslider_navigations_bkp` because it could not be opened.
2025-06-10T12:22:15.291706Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.292007Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.292266Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.292790Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_revslider_sliders.ibd' OS error: 103
2025-06-10T12:22:15.293178Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.293468Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.293888Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_revslider_sliders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.294549Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_revslider_sliders` because it could not be opened.
2025-06-10T12:22:15.295003Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.295266Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.295635Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.296073Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_revslider_sliders_bkp.ibd' OS error: 103
2025-06-10T12:22:15.296512Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.296779Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.297181Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_revslider_sliders_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.297907Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_revslider_sliders_bkp` because it could not be opened.
2025-06-10T12:22:15.298359Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.298639Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.298967Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.299433Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_revslider_slides.ibd' OS error: 103
2025-06-10T12:22:15.299780Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.300125Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.300542Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_revslider_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.301089Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_revslider_slides` because it could not be opened.
2025-06-10T12:22:15.301662Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.301920Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.302174Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.302645Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_revslider_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:15.302983Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.303230Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.303714Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_revslider_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.304271Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_revslider_slides_bkp` because it could not be opened.
2025-06-10T12:22:15.304745Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.305075Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.305463Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.305845Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_revslider_static_slides.ibd' OS error: 103
2025-06-10T12:22:15.306381Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.306647Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.307057Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_revslider_static_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.307687Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_revslider_static_slides` because it could not be opened.
2025-06-10T12:22:15.308095Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.308437Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.308709Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.309068Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_revslider_static_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:15.309517Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.309781Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.310177Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_revslider_static_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.311128Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_revslider_static_slides_bkp` because it could not be opened.
2025-06-10T12:22:15.311742Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.311994Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.312251Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.312717Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:15.313058Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.313385Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.313797Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.314551Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:15.314986Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.315241Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.315581Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.315943Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:15.316439Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.316709Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.317103Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.317860Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:15.318260Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.318567Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.318819Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.319175Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:15.319607Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.319849Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.320233Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.320886Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_termmeta` because it could not be opened.
2025-06-10T12:22:15.321279Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.321591Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.321842Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.322773Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_terms.ibd' OS error: 103
2025-06-10T12:22:15.323179Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.323499Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.323903Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.324500Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_terms` because it could not be opened.
2025-06-10T12:22:15.324873Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.325175Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.325446Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.325825Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:15.326239Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.326513Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.326934Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.327557Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_usermeta` because it could not be opened.
2025-06-10T12:22:15.328105Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.328374Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.328644Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.329026Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_users.ibd' OS error: 103
2025-06-10T12:22:15.329383Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.329646Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.330109Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.330664Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_users` because it could not be opened.
2025-06-10T12:22:15.331104Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.331405Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.331719Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.332187Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_wc_admin_note_actions.ibd' OS error: 103
2025-06-10T12:22:15.332604Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.332878Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.333390Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_wc_admin_note_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.334104Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_wc_admin_note_actions` because it could not be opened.
2025-06-10T12:22:15.334663Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.335084Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.335381Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.335857Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_wc_admin_notes.ibd' OS error: 103
2025-06-10T12:22:15.336318Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.336620Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.337013Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_wc_admin_notes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.337676Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_wc_admin_notes` because it could not be opened.
2025-06-10T12:22:15.338222Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.338506Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.338762Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.339281Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_wc_category_lookup.ibd' OS error: 103
2025-06-10T12:22:15.339611Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.339855Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.340450Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_wc_category_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.341314Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_wc_category_lookup` because it could not be opened.
2025-06-10T12:22:15.341732Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.341979Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.342344Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.342726Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_wc_customer_lookup.ibd' OS error: 103
2025-06-10T12:22:15.343169Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.343431Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.343825Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_wc_customer_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.344474Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_wc_customer_lookup` because it could not be opened.
2025-06-10T12:22:15.344841Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.345214Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.345485Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.346096Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_wc_download_log.ibd' OS error: 103
2025-06-10T12:22:15.346523Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.346774Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.347286Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_wc_download_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.347839Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_wc_download_log` because it could not be opened.
2025-06-10T12:22:15.348380Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.348633Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.348887Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.349377Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_wc_order_coupon_lookup.ibd' OS error: 103
2025-06-10T12:22:15.349850Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.350280Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.350671Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_wc_order_coupon_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.351432Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_wc_order_coupon_lookup` because it could not be opened.
2025-06-10T12:22:15.351915Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.352296Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.352554Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.353077Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_wc_order_product_lookup.ibd' OS error: 103
2025-06-10T12:22:15.353552Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.353804Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.354328Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_wc_order_product_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.354877Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_wc_order_product_lookup` because it could not be opened.
2025-06-10T12:22:15.355461Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.355837Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.356091Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.356951Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_wc_order_stats.ibd' OS error: 103
2025-06-10T12:22:15.357328Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.357659Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.358453Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_wc_order_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.359451Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_wc_order_stats` because it could not be opened.
2025-06-10T12:22:15.360082Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.360432Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.360771Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.361159Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_wc_order_tax_lookup.ibd' OS error: 103
2025-06-10T12:22:15.361557Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.361819Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.362254Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_wc_order_tax_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.362841Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_wc_order_tax_lookup` because it could not be opened.
2025-06-10T12:22:15.363293Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.363563Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.363839Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.364256Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_wc_product_meta_lookup.ibd' OS error: 103
2025-06-10T12:22:15.364626Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.364889Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.365351Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_wc_product_meta_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.365992Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_wc_product_meta_lookup` because it could not be opened.
2025-06-10T12:22:15.366491Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.366768Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.367067Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.367473Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_wc_reserved_stock.ibd' OS error: 103
2025-06-10T12:22:15.367855Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.368119Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.368680Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_wc_reserved_stock`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.369298Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_wc_reserved_stock` because it could not be opened.
2025-06-10T12:22:15.369738Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.370007Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.370295Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.370672Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_wc_tax_rate_classes.ibd' OS error: 103
2025-06-10T12:22:15.371026Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.371327Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.371737Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_wc_tax_rate_classes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.372618Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_wc_tax_rate_classes` because it could not be opened.
2025-06-10T12:22:15.373070Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.373453Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.373767Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.374139Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_wc_webhooks.ibd' OS error: 103
2025-06-10T12:22:15.374537Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.374792Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.375266Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_wc_webhooks`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.375844Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_wc_webhooks` because it could not be opened.
2025-06-10T12:22:15.376322Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.376580Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.376839Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.377256Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_woocommerce_api_keys.ibd' OS error: 103
2025-06-10T12:22:15.377612Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.377862Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.378339Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_woocommerce_api_keys`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.378994Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_woocommerce_api_keys` because it could not be opened.
2025-06-10T12:22:15.379507Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.379808Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.380086Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.380553Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_woocommerce_attribute_taxonomies.ibd' OS error: 103
2025-06-10T12:22:15.380925Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.381232Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.381650Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_woocommerce_attribute_taxonomies`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.382296Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_woocommerce_attribute_taxonomies` because it could not be opened.
2025-06-10T12:22:15.382742Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.382996Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.383353Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.383721Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_woocommerce_downloadable_product_permissions.ibd' OS error: 103
2025-06-10T12:22:15.384117Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.384479Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.384920Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_woocommerce_downloadable_product_permissions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.385593Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_woocommerce_downloadable_product_permissions` because it could not be opened.
2025-06-10T12:22:15.386073Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.386462Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.386822Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.387518Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_woocommerce_log.ibd' OS error: 103
2025-06-10T12:22:15.388244Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.388594Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.390574Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_woocommerce_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.391316Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_woocommerce_log` because it could not be opened.
2025-06-10T12:22:15.391763Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.392061Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.392340Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.392731Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_woocommerce_order_itemmeta.ibd' OS error: 103
2025-06-10T12:22:15.393126Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.393390Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.393803Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_woocommerce_order_itemmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.394432Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_woocommerce_order_itemmeta` because it could not be opened.
2025-06-10T12:22:15.394911Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.395180Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.395447Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.395837Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_woocommerce_order_items.ibd' OS error: 103
2025-06-10T12:22:15.396216Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.396483Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.397000Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_woocommerce_order_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.397611Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_woocommerce_order_items` because it could not be opened.
2025-06-10T12:22:15.398132Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.398423Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.398701Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.399135Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_woocommerce_payment_tokenmeta.ibd' OS error: 103
2025-06-10T12:22:15.399517Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.399824Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.400240Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_woocommerce_payment_tokenmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.400875Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_woocommerce_payment_tokenmeta` because it could not be opened.
2025-06-10T12:22:15.401327Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.401588Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.401881Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.402270Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_woocommerce_payment_tokens.ibd' OS error: 103
2025-06-10T12:22:15.402627Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.402912Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.403320Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_woocommerce_payment_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.403943Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_woocommerce_payment_tokens` because it could not be opened.
2025-06-10T12:22:15.404401Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.404665Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.404975Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.405391Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_woocommerce_sessions.ibd' OS error: 103
2025-06-10T12:22:15.405972Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.406251Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.406662Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_woocommerce_sessions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.407276Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_woocommerce_sessions` because it could not be opened.
2025-06-10T12:22:15.407697Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.407987Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.408257Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.408638Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_woocommerce_shipping_zone_locations.ibd' OS error: 103
2025-06-10T12:22:15.409050Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.409308Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.409716Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_woocommerce_shipping_zone_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.410555Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_woocommerce_shipping_zone_locations` because it could not be opened.
2025-06-10T12:22:15.411312Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.411692Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.412181Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.412802Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_woocommerce_shipping_zone_methods.ibd' OS error: 103
2025-06-10T12:22:15.413326Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.413618Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.414180Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_woocommerce_shipping_zone_methods`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.414813Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_woocommerce_shipping_zone_methods` because it could not be opened.
2025-06-10T12:22:15.415338Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.415592Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.415901Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.416280Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_woocommerce_shipping_zones.ibd' OS error: 103
2025-06-10T12:22:15.416630Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.416964Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.417370Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_woocommerce_shipping_zones`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.418042Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_woocommerce_shipping_zones` because it could not be opened.
2025-06-10T12:22:15.418448Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.418700Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.419051Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.419693Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_woocommerce_tax_rate_locations.ibd' OS error: 103
2025-06-10T12:22:15.420520Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.420787Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.421681Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_woocommerce_tax_rate_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.422935Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_woocommerce_tax_rate_locations` because it could not be opened.
2025-06-10T12:22:15.423873Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.424142Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.424429Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.424853Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_woocommerce_tax_rates.ibd' OS error: 103
2025-06-10T12:22:15.425268Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.425569Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.425989Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_woocommerce_tax_rates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.426621Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_woocommerce_tax_rates` because it could not be opened.
2025-06-10T12:22:15.427182Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.427620Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.427933Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.428311Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:15.428841Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.429100Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.429648Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.430574Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:15.431108Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.431461Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.431753Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.432137Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:15.432551Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.432823Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.433247Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.433938Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:15.434414Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.434701Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.434971Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.435358Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:15.435769Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.436084Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.436555Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.437201Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:15.437727Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.438009Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.438312Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.438712Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:15.439076Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.439339Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.439783Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.440397Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:15.440837Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.441103Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.441388Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.441796Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_yoast_indexable.ibd' OS error: 103
2025-06-10T12:22:15.442164Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.442453Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.442970Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_yoast_indexable`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.443825Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_yoast_indexable` because it could not be opened.
2025-06-10T12:22:15.444300Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.444595Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.444902Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.445297Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_yoast_indexable_hierarchy.ibd' OS error: 103
2025-06-10T12:22:15.445687Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.445956Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.446385Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_yoast_indexable_hierarchy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.447030Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_yoast_indexable_hierarchy` because it could not be opened.
2025-06-10T12:22:15.447496Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.447760Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.448031Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.448446Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_yoast_migrations.ibd' OS error: 103
2025-06-10T12:22:15.448794Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.449054Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.449494Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_yoast_migrations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.450225Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_yoast_migrations` because it could not be opened.
2025-06-10T12:22:15.451600Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.451903Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.453220Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.455043Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_yoast_primary_term.ibd' OS error: 103
2025-06-10T12:22:15.455491Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.455773Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.456406Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_yoast_primary_term`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.457062Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_yoast_primary_term` because it could not be opened.
2025-06-10T12:22:15.457502Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.457769Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.458107Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.458544Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech3\wp_yoast_seo_links.ibd' OS error: 103
2025-06-10T12:22:15.458932Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.459196Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.459602Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech3/wp_yoast_seo_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.460227Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech3/wp_yoast_seo_links` because it could not be opened.
2025-06-10T12:22:15.461111Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.461475Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.461774Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.462216Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_actionscheduler_actions.ibd' OS error: 103
2025-06-10T12:22:15.462585Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.462880Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.463322Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_actionscheduler_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.463973Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_actionscheduler_actions` because it could not be opened.
2025-06-10T12:22:15.464496Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.464795Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.465133Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.465520Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_actionscheduler_claims.ibd' OS error: 103
2025-06-10T12:22:15.465948Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.466210Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.466621Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_actionscheduler_claims`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.467276Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_actionscheduler_claims` because it could not be opened.
2025-06-10T12:22:15.467724Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.468045Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.468316Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.468695Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_actionscheduler_groups.ibd' OS error: 103
2025-06-10T12:22:15.469111Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.469367Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.469771Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_actionscheduler_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.470417Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_actionscheduler_groups` because it could not be opened.
2025-06-10T12:22:15.470890Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.471157Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.471423Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.471841Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_actionscheduler_logs.ibd' OS error: 103
2025-06-10T12:22:15.472251Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.472538Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.472995Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_actionscheduler_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.473595Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_actionscheduler_logs` because it could not be opened.
2025-06-10T12:22:15.474072Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.474506Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.474795Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.475271Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:15.475620Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.475961Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.476394Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.477043Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:15.477756Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.478082Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.478642Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.479090Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_comments.ibd' OS error: 103
2025-06-10T12:22:15.479426Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.479692Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.480148Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.480717Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_comments` because it could not be opened.
2025-06-10T12:22:15.481152Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.481421Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.481691Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.482173Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:15.482567Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.482964Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.483457Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.485890Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_fbv` because it could not be opened.
2025-06-10T12:22:15.486364Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.487084Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.487549Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.487944Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:15.488328Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.488649Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.489057Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.489695Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:15.490255Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.490548Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.490819Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.491205Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_itsec_bans.ibd' OS error: 103
2025-06-10T12:22:15.491580Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.491841Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.492262Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_itsec_bans`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.492910Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_itsec_bans` because it could not be opened.
2025-06-10T12:22:15.493348Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.493669Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.493947Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.494325Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_itsec_dashboard_events.ibd' OS error: 103
2025-06-10T12:22:15.494831Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.495092Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.495578Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_itsec_dashboard_events`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.496146Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_itsec_dashboard_events` because it could not be opened.
2025-06-10T12:22:15.496745Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.497018Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.497276Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.497721Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_itsec_distributed_storage.ibd' OS error: 103
2025-06-10T12:22:15.498104Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.498397Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.498821Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_itsec_distributed_storage`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.499473Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_itsec_distributed_storage` because it could not be opened.
2025-06-10T12:22:15.500014Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.500378Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.500683Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.501077Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_itsec_fingerprints.ibd' OS error: 103
2025-06-10T12:22:15.501473Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.501736Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.502150Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_itsec_fingerprints`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.502780Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_itsec_fingerprints` because it could not be opened.
2025-06-10T12:22:15.503220Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.503514Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.503783Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.504166Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_itsec_geolocation_cache.ibd' OS error: 103
2025-06-10T12:22:15.504551Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.504810Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.505216Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_itsec_geolocation_cache`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.505872Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_itsec_geolocation_cache` because it could not be opened.
2025-06-10T12:22:15.506549Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.506902Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.507173Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.507639Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_itsec_lockouts.ibd' OS error: 103
2025-06-10T12:22:15.507963Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.508211Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.508683Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_itsec_lockouts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.509464Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_itsec_lockouts` because it could not be opened.
2025-06-10T12:22:15.509885Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.510148Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.510452Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.510834Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_itsec_logs.ibd' OS error: 103
2025-06-10T12:22:15.511150Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.511459Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.511923Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_itsec_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.512633Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_itsec_logs` because it could not be opened.
2025-06-10T12:22:15.513005Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.513255Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.513587Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.513969Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_itsec_mutexes.ibd' OS error: 103
2025-06-10T12:22:15.514312Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.514622Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.515016Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_itsec_mutexes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.515668Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_itsec_mutexes` because it could not be opened.
2025-06-10T12:22:15.516046Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.516307Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.516757Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.517210Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_itsec_opaque_tokens.ibd' OS error: 103
2025-06-10T12:22:15.517636Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.517884Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.518272Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_itsec_opaque_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.518965Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_itsec_opaque_tokens` because it could not be opened.
2025-06-10T12:22:15.519432Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.519724Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.519989Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.520442Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_itsec_temp.ibd' OS error: 103
2025-06-10T12:22:15.520774Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.521125Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.521647Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_itsec_temp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.522194Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_itsec_temp` because it could not be opened.
2025-06-10T12:22:15.522685Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.522946Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.523209Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.523674Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_itsec_user_groups.ibd' OS error: 103
2025-06-10T12:22:15.524010Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.524261Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.524850Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_itsec_user_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.525583Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_itsec_user_groups` because it could not be opened.
2025-06-10T12:22:15.526073Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.526422Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.526699Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.527069Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_links.ibd' OS error: 103
2025-06-10T12:22:15.527504Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.527791Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.528187Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.528852Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_links` because it could not be opened.
2025-06-10T12:22:15.529480Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.529772Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.530050Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.530513Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_options.ibd' OS error: 103
2025-06-10T12:22:15.530881Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.531146Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.531996Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.533035Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_options` because it could not be opened.
2025-06-10T12:22:15.533674Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.534069Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.534420Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.534907Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_post_views.ibd' OS error: 103
2025-06-10T12:22:15.535350Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.535738Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.536182Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_post_views`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.536821Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_post_views` because it could not be opened.
2025-06-10T12:22:15.537260Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.537532Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.537887Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.538269Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:15.538602Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.538932Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.539349Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.539983Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_postmeta` because it could not be opened.
2025-06-10T12:22:15.540664Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.541011Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.541285Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.541667Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_posts.ibd' OS error: 103
2025-06-10T12:22:15.542066Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.542336Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.542831Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.543463Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_posts` because it could not be opened.
2025-06-10T12:22:15.543936Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.544200Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.544472Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.544996Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_revslider_css.ibd' OS error: 103
2025-06-10T12:22:15.545377Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.545648Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.546111Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_revslider_css`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.546708Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_revslider_css` because it could not be opened.
2025-06-10T12:22:15.547133Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.547390Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.547651Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.548114Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_revslider_css_bkp.ibd' OS error: 103
2025-06-10T12:22:15.548444Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.548719Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.549149Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_revslider_css_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.549773Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_revslider_css_bkp` because it could not be opened.
2025-06-10T12:22:15.550179Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.550434Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.550726Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.551154Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_revslider_layer_animations.ibd' OS error: 103
2025-06-10T12:22:15.551505Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.551809Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.552248Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_revslider_layer_animations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.552917Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_revslider_layer_animations` because it could not be opened.
2025-06-10T12:22:15.553388Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.553676Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.554198Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.554587Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_revslider_layer_animations_bkp.ibd' OS error: 103
2025-06-10T12:22:15.555118Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.555416Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.555982Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_revslider_layer_animations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.556570Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_revslider_layer_animations_bkp` because it could not be opened.
2025-06-10T12:22:15.557140Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.557439Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.557874Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.558264Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_revslider_navigations.ibd' OS error: 103
2025-06-10T12:22:15.558628Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.558950Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.559436Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_revslider_navigations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.560069Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_revslider_navigations` because it could not be opened.
2025-06-10T12:22:15.560581Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.560884Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.561158Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.561543Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_revslider_navigations_bkp.ibd' OS error: 103
2025-06-10T12:22:15.561953Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.562215Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.562627Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_revslider_navigations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.563325Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_revslider_navigations_bkp` because it could not be opened.
2025-06-10T12:22:15.565136Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.566542Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.567522Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.568167Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_revslider_sliders.ibd' OS error: 103
2025-06-10T12:22:15.568607Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.568944Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.569360Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_revslider_sliders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.570201Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_revslider_sliders` because it could not be opened.
2025-06-10T12:22:15.570621Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.570971Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.571317Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.571685Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_revslider_sliders_bkp.ibd' OS error: 103
2025-06-10T12:22:15.572102Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.572368Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.572848Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_revslider_sliders_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.573461Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_revslider_sliders_bkp` because it could not be opened.
2025-06-10T12:22:15.573989Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.574261Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.574535Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.574990Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_revslider_slides.ibd' OS error: 103
2025-06-10T12:22:15.575394Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.575702Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.576183Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_revslider_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.576777Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_revslider_slides` because it could not be opened.
2025-06-10T12:22:15.577260Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.577528Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.577854Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.578241Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_revslider_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:15.578597Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.578885Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.579294Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_revslider_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.579912Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_revslider_slides_bkp` because it could not be opened.
2025-06-10T12:22:15.580319Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.580581Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.580878Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.581257Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_revslider_static_slides.ibd' OS error: 103
2025-06-10T12:22:15.581723Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.582087Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.582479Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_revslider_static_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.583121Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_revslider_static_slides` because it could not be opened.
2025-06-10T12:22:15.583532Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.583844Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.584117Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.584500Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_revslider_static_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:15.584908Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.585169Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.585583Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_revslider_static_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.586249Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_revslider_static_slides_bkp` because it could not be opened.
2025-06-10T12:22:15.586664Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.586987Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.587248Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.587616Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:15.588072Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.588347Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.588816Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.589411Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:15.589965Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.590237Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.590510Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.590933Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:15.591274Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.591536Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.592029Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.592610Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:15.593052Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.593320Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.593587Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.594055Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:15.594569Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.594961Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.595583Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.596545Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_termmeta` because it could not be opened.
2025-06-10T12:22:15.597233Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.598355Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.598645Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.599178Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_terms.ibd' OS error: 103
2025-06-10T12:22:15.599513Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.599791Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.600334Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.600993Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_terms` because it could not be opened.
2025-06-10T12:22:15.601401Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.601666Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.602019Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.602405Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:15.602732Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.603061Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.603473Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.604096Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_usermeta` because it could not be opened.
2025-06-10T12:22:15.604523Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.604791Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.605110Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.605513Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_users.ibd' OS error: 103
2025-06-10T12:22:15.605880Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.606150Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.606581Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.607327Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_users` because it could not be opened.
2025-06-10T12:22:15.607727Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.608037Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.608363Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.608840Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_wc_admin_note_actions.ibd' OS error: 103
2025-06-10T12:22:15.609217Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.609476Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.609917Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_wc_admin_note_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.610556Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_wc_admin_note_actions` because it could not be opened.
2025-06-10T12:22:15.611077Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.611347Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.611618Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.612106Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_wc_admin_notes.ibd' OS error: 103
2025-06-10T12:22:15.612447Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.612745Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.613201Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_wc_admin_notes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.613834Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_wc_admin_notes` because it could not be opened.
2025-06-10T12:22:15.614279Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.614576Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.614882Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.615268Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_wc_category_lookup.ibd' OS error: 103
2025-06-10T12:22:15.615618Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.615911Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.616323Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_wc_category_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.616944Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_wc_category_lookup` because it could not be opened.
2025-06-10T12:22:15.617346Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.617612Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.617915Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.618297Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_wc_customer_lookup.ibd' OS error: 103
2025-06-10T12:22:15.618648Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.618951Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.619370Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_wc_customer_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.619992Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_wc_customer_lookup` because it could not be opened.
2025-06-10T12:22:15.620485Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.620849Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.621141Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.621510Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_wc_download_log.ibd' OS error: 103
2025-06-10T12:22:15.621917Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.622180Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.622587Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_wc_download_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.623270Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_wc_download_log` because it could not be opened.
2025-06-10T12:22:15.623705Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.624090Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.624363Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.624741Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_wc_order_coupon_lookup.ibd' OS error: 103
2025-06-10T12:22:15.625168Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.625431Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.625908Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_wc_order_coupon_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.626781Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_wc_order_coupon_lookup` because it could not be opened.
2025-06-10T12:22:15.627991Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.628487Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.629016Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.629473Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_wc_order_product_lookup.ibd' OS error: 103
2025-06-10T12:22:15.629836Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.630444Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.630882Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_wc_order_product_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.631706Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_wc_order_product_lookup` because it could not be opened.
2025-06-10T12:22:15.632172Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.632462Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.632744Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.633151Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_wc_order_stats.ibd' OS error: 103
2025-06-10T12:22:15.633492Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.633755Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.634233Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_wc_order_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.634913Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_wc_order_stats` because it could not be opened.
2025-06-10T12:22:15.635374Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.635644Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.636015Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.636405Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_wc_order_tax_lookup.ibd' OS error: 103
2025-06-10T12:22:15.636748Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.637081Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.637502Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_wc_order_tax_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.638246Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_wc_order_tax_lookup` because it could not be opened.
2025-06-10T12:22:15.638786Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.639109Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.639391Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.639755Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_wc_product_meta_lookup.ibd' OS error: 103
2025-06-10T12:22:15.640192Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.640443Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.640859Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_wc_product_meta_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.641572Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_wc_product_meta_lookup` because it could not be opened.
2025-06-10T12:22:15.642055Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.642309Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.642567Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.643044Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_wc_reserved_stock.ibd' OS error: 103
2025-06-10T12:22:15.643393Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.643647Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.644146Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_wc_reserved_stock`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.644768Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_wc_reserved_stock` because it could not be opened.
2025-06-10T12:22:15.645323Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.645578Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.645882Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.646268Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_wc_tax_rate_classes.ibd' OS error: 103
2025-06-10T12:22:15.646621Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.646922Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.647342Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_wc_tax_rate_classes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.647968Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_wc_tax_rate_classes` because it could not be opened.
2025-06-10T12:22:15.648349Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.648602Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.648937Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.649316Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_wc_webhooks.ibd' OS error: 103
2025-06-10T12:22:15.649634Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.649961Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.650402Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_wc_webhooks`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.651006Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_wc_webhooks` because it could not be opened.
2025-06-10T12:22:15.651395Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.651661Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.651975Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.652360Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_woocommerce_api_keys.ibd' OS error: 103
2025-06-10T12:22:15.652733Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.653073Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.653573Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_woocommerce_api_keys`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.654259Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_woocommerce_api_keys` because it could not be opened.
2025-06-10T12:22:15.654737Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.655099Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.655480Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.655869Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_woocommerce_attribute_taxonomies.ibd' OS error: 103
2025-06-10T12:22:15.656238Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.656614Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.657013Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_woocommerce_attribute_taxonomies`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.657744Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_woocommerce_attribute_taxonomies` because it could not be opened.
2025-06-10T12:22:15.658190Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.658566Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.658876Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.659444Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_woocommerce_downloadable_product_permissions.ibd' OS error: 103
2025-06-10T12:22:15.659991Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.660248Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.660727Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_woocommerce_downloadable_product_permissions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.661821Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_woocommerce_downloadable_product_permissions` because it could not be opened.
2025-06-10T12:22:15.662747Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.663756Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.664210Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.664662Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_woocommerce_log.ibd' OS error: 103
2025-06-10T12:22:15.665028Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.665437Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.665942Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_woocommerce_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.666668Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_woocommerce_log` because it could not be opened.
2025-06-10T12:22:15.667154Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.667441Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.667722Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.668108Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_woocommerce_order_itemmeta.ibd' OS error: 103
2025-06-10T12:22:15.668524Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.668790Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.669257Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_woocommerce_order_itemmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.669987Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_woocommerce_order_itemmeta` because it could not be opened.
2025-06-10T12:22:15.670638Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.670925Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.671347Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.671798Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_woocommerce_order_items.ibd' OS error: 103
2025-06-10T12:22:15.672395Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.672667Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.673080Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_woocommerce_order_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.673708Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_woocommerce_order_items` because it could not be opened.
2025-06-10T12:22:15.674175Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.674444Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.674713Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.675126Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_woocommerce_payment_tokenmeta.ibd' OS error: 103
2025-06-10T12:22:15.675504Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.675765Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.676228Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_woocommerce_payment_tokenmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.676972Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_woocommerce_payment_tokenmeta` because it could not be opened.
2025-06-10T12:22:15.677478Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.677752Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.678027Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.678439Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_woocommerce_payment_tokens.ibd' OS error: 103
2025-06-10T12:22:15.678804Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.679066Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.679512Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_woocommerce_payment_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.680150Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_woocommerce_payment_tokens` because it could not be opened.
2025-06-10T12:22:15.680583Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.680846Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.681151Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.681537Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_woocommerce_sessions.ibd' OS error: 103
2025-06-10T12:22:15.681885Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.682177Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.682612Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_woocommerce_sessions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.683368Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_woocommerce_sessions` because it could not be opened.
2025-06-10T12:22:15.683810Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.684065Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.684441Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.684806Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_woocommerce_shipping_zone_locations.ibd' OS error: 103
2025-06-10T12:22:15.685304Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.685589Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.686040Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_woocommerce_shipping_zone_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.686742Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_woocommerce_shipping_zone_locations` because it could not be opened.
2025-06-10T12:22:15.687292Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.687573Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.687837Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.688270Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_woocommerce_shipping_zone_methods.ibd' OS error: 103
2025-06-10T12:22:15.688638Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.689014Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.689480Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_woocommerce_shipping_zone_methods`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.690218Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_woocommerce_shipping_zone_methods` because it could not be opened.
2025-06-10T12:22:15.690676Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.691124Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.691383Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.691918Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_woocommerce_shipping_zones.ibd' OS error: 103
2025-06-10T12:22:15.692710Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.693017Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.693973Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_woocommerce_shipping_zones`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.695043Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_woocommerce_shipping_zones` because it could not be opened.
2025-06-10T12:22:15.695794Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.696094Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.696369Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.696767Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_woocommerce_tax_rate_locations.ibd' OS error: 103
2025-06-10T12:22:15.697175Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.697453Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.698005Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_woocommerce_tax_rate_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.698672Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_woocommerce_tax_rate_locations` because it could not be opened.
2025-06-10T12:22:15.699142Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.699447Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.699725Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.700115Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_woocommerce_tax_rates.ibd' OS error: 103
2025-06-10T12:22:15.700524Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.700794Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.701215Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_woocommerce_tax_rates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.701935Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_woocommerce_tax_rates` because it could not be opened.
2025-06-10T12:22:15.702606Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.702888Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.703196Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.703600Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:15.703957Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.704328Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.704852Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.705487Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:15.705913Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.706172Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.706495Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.706870Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:15.707191Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.707501Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.707899Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.708545Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:15.708914Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.709167Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.709490Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.710000Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:15.710590Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.710858Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.711253Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.711853Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:15.712481Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.712823Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.713082Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.713520Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:15.713912Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.714164Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.714647Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.715218Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:15.715756Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.716009Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.716275Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.716838Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_yoast_indexable.ibd' OS error: 103
2025-06-10T12:22:15.717193Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.717516Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.717963Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_yoast_indexable`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.718584Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_yoast_indexable` because it could not be opened.
2025-06-10T12:22:15.718994Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.719260Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.719571Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.719959Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_yoast_indexable_hierarchy.ibd' OS error: 103
2025-06-10T12:22:15.720338Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.720621Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.721035Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_yoast_indexable_hierarchy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.721666Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_yoast_indexable_hierarchy` because it could not be opened.
2025-06-10T12:22:15.722077Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.722371Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.722735Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.723135Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_yoast_migrations.ibd' OS error: 103
2025-06-10T12:22:15.723553Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.723806Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.724194Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_yoast_migrations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.724851Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_yoast_migrations` because it could not be opened.
2025-06-10T12:22:15.725224Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.725550Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.725813Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.726178Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_yoast_primary_term.ibd' OS error: 103
2025-06-10T12:22:15.726617Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.726868Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.727351Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_yoast_primary_term`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.727942Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_yoast_primary_term` because it could not be opened.
2025-06-10T12:22:15.728377Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.728660Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.728936Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.729334Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_acetech4\wp_yoast_seo_links.ibd' OS error: 103
2025-06-10T12:22:15.729786Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.730046Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.730491Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_acetech4/wp_yoast_seo_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.731067Z 0 [Warning] InnoDB: Ignoring tablespace `client_acetech4/wp_yoast_seo_links` because it could not be opened.
2025-06-10T12:22:15.731827Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.732135Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.732482Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.732893Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_actionscheduler_actions.ibd' OS error: 103
2025-06-10T12:22:15.733267Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.733626Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.734020Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_actionscheduler_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.734652Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_actionscheduler_actions` because it could not be opened.
2025-06-10T12:22:15.735254Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.735743Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.736029Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.736445Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_actionscheduler_claims.ibd' OS error: 103
2025-06-10T12:22:15.736804Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.737066Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.737508Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_actionscheduler_claims`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.738141Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_actionscheduler_claims` because it could not be opened.
2025-06-10T12:22:15.738583Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.739489Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.739765Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.740205Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_actionscheduler_groups.ibd' OS error: 103
2025-06-10T12:22:15.740680Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.741474Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.741888Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_actionscheduler_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.742657Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_actionscheduler_groups` because it could not be opened.
2025-06-10T12:22:15.743123Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.743395Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.743706Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.744086Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_actionscheduler_logs.ibd' OS error: 103
2025-06-10T12:22:15.744442Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.744734Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.745150Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_actionscheduler_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.745802Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_actionscheduler_logs` because it could not be opened.
2025-06-10T12:22:15.746251Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.746548Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.746821Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.747219Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:15.747611Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.747894Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.748329Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.749158Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:15.749812Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.750123Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.750429Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.750891Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_comments.ibd' OS error: 103
2025-06-10T12:22:15.751299Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.751681Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.752136Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.752742Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_comments` because it could not be opened.
2025-06-10T12:22:15.753145Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.753398Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.753727Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.754092Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:15.754396Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.754724Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.755135Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.755748Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_fbv` because it could not be opened.
2025-06-10T12:22:15.756107Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.756360Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.756756Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.757154Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:15.757547Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.757840Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.758234Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.758908Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:15.759301Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.759645Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.759902Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.760265Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_links.ibd' OS error: 103
2025-06-10T12:22:15.760637Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.760886Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.761275Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.761900Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_links` because it could not be opened.
2025-06-10T12:22:15.762394Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.762758Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.763031Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.763396Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_ninja_charts.ibd' OS error: 103
2025-06-10T12:22:15.764008Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.764387Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.764930Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_ninja_charts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.765609Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_ninja_charts` because it could not be opened.
2025-06-10T12:22:15.766068Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.766322Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.766636Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.767023Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_ninja_table_items.ibd' OS error: 103
2025-06-10T12:22:15.767367Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.767665Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.768058Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_ninja_table_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.768675Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_ninja_table_items` because it could not be opened.
2025-06-10T12:22:15.769458Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.769747Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.770024Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.770430Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_options.ibd' OS error: 103
2025-06-10T12:22:15.771823Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.772576Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.773145Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.774003Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_options` because it could not be opened.
2025-06-10T12:22:15.775259Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.775535Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.775853Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.776256Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_post_views.ibd' OS error: 103
2025-06-10T12:22:15.776607Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.776872Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.777479Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_post_views`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.778092Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_post_views` because it could not be opened.
2025-06-10T12:22:15.778592Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.778872Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.779149Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.779559Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:15.779917Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.780308Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.780749Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.781360Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_postmeta` because it could not be opened.
2025-06-10T12:22:15.781791Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.782066Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.782440Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.782832Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_posts.ibd' OS error: 103
2025-06-10T12:22:15.783169Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.783465Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.783876Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.784462Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_posts` because it could not be opened.
2025-06-10T12:22:15.784857Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.785121Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.785515Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.785898Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_revslider_css.ibd' OS error: 103
2025-06-10T12:22:15.786249Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.786508Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.786919Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_revslider_css`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.787529Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_revslider_css` because it could not be opened.
2025-06-10T12:22:15.787927Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.788216Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.788494Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.788875Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_revslider_css_bkp.ibd' OS error: 103
2025-06-10T12:22:15.789245Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.789505Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.789948Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_revslider_css_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.790596Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_revslider_css_bkp` because it could not be opened.
2025-06-10T12:22:15.791036Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.791359Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.791617Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.791984Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_revslider_layer_animations.ibd' OS error: 103
2025-06-10T12:22:15.792400Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.792667Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.793060Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_revslider_layer_animations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.793711Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_revslider_layer_animations` because it could not be opened.
2025-06-10T12:22:15.794113Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.794485Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.794787Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.795270Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_revslider_layer_animations_bkp.ibd' OS error: 103
2025-06-10T12:22:15.795647Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.795898Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.796432Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_revslider_layer_animations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.797109Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_revslider_layer_animations_bkp` because it could not be opened.
2025-06-10T12:22:15.797758Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.798037Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.798442Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.798926Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_revslider_navigations.ibd' OS error: 103
2025-06-10T12:22:15.799316Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.799597Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.799990Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_revslider_navigations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.800698Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_revslider_navigations` because it could not be opened.
2025-06-10T12:22:15.801293Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.801584Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.801881Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.802298Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_revslider_navigations_bkp.ibd' OS error: 103
2025-06-10T12:22:15.802661Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.802935Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.803370Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_revslider_navigations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.804020Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_revslider_navigations_bkp` because it could not be opened.
2025-06-10T12:22:15.804524Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.804785Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.805134Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.805696Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_revslider_sliders.ibd' OS error: 103
2025-06-10T12:22:15.806626Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.806887Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.807899Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_revslider_sliders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.808539Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_revslider_sliders` because it could not be opened.
2025-06-10T12:22:15.809065Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.809379Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.809668Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.810050Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_revslider_sliders_bkp.ibd' OS error: 103
2025-06-10T12:22:15.810624Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.810905Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.811350Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_revslider_sliders_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.811933Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_revslider_sliders_bkp` because it could not be opened.
2025-06-10T12:22:15.812481Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.812775Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.813044Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.813510Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_revslider_slides.ibd' OS error: 103
2025-06-10T12:22:15.813843Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.814094Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.814623Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_revslider_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.815224Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_revslider_slides` because it could not be opened.
2025-06-10T12:22:15.815745Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.816014Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.816331Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.816709Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_revslider_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:15.817070Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.817367Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.817770Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_revslider_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.818407Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_revslider_slides_bkp` because it could not be opened.
2025-06-10T12:22:15.818810Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.819058Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.819387Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.819808Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_revslider_static_slides.ibd' OS error: 103
2025-06-10T12:22:15.820148Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.820475Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.820865Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_revslider_static_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.821483Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_revslider_static_slides` because it could not be opened.
2025-06-10T12:22:15.821891Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.822288Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.822658Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.823062Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_revslider_static_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:15.823537Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.823937Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.824420Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_revslider_static_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.824992Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_revslider_static_slides_bkp` because it could not be opened.
2025-06-10T12:22:15.825499Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.825843Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.826097Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.826595Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_sbi_instagram_feeds_posts.ibd' OS error: 103
2025-06-10T12:22:15.826997Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.827306Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.827785Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_sbi_instagram_feeds_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.828501Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_sbi_instagram_feeds_posts` because it could not be opened.
2025-06-10T12:22:15.828956Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.829257Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.829557Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.829913Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_sbi_instagram_posts.ibd' OS error: 103
2025-06-10T12:22:15.830494Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.830764Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.831159Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_sbi_instagram_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.831776Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_sbi_instagram_posts` because it could not be opened.
2025-06-10T12:22:15.832172Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.832516Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.832771Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.833160Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:15.833547Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.833791Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.834230Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.835100Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:15.835643Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.835981Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.836255Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.837258Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:15.838336Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.838607Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.839062Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.839636Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:15.840068Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.840329Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.840592Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.841019Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:15.841343Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.841603Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.842078Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.842645Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_termmeta` because it could not be opened.
2025-06-10T12:22:15.843174Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.843439Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.843708Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.844145Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_terms.ibd' OS error: 103
2025-06-10T12:22:15.844473Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.844929Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.845384Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.846003Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_terms` because it could not be opened.
2025-06-10T12:22:15.846454Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.846756Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.847044Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.847423Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_ts_advancedstyles.ibd' OS error: 103
2025-06-10T12:22:15.847771Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.848059Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.848472Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_ts_advancedstyles`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.849143Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_ts_advancedstyles` because it could not be opened.
2025-06-10T12:22:15.849563Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.849860Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.850172Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.850541Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_ts_advancedtables.ibd' OS error: 103
2025-06-10T12:22:15.850921Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.851186Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.851617Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_ts_advancedtables`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.852304Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_ts_advancedtables` because it could not be opened.
2025-06-10T12:22:15.852688Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.853069Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.853384Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.853769Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:15.854132Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.854395Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.854823Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.855411Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_usermeta` because it could not be opened.
2025-06-10T12:22:15.855823Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.856093Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.856361Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.856742Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_users.ibd' OS error: 103
2025-06-10T12:22:15.857125Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.857390Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.857995Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.858606Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_users` because it could not be opened.
2025-06-10T12:22:15.859074Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.859339Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.859700Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.860118Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_wc_admin_note_actions.ibd' OS error: 103
2025-06-10T12:22:15.860485Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.860815Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.861236Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_wc_admin_note_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.861877Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_wc_admin_note_actions` because it could not be opened.
2025-06-10T12:22:15.862337Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.862592Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.862929Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.863304Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_wc_admin_notes.ibd' OS error: 103
2025-06-10T12:22:15.863626Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.863935Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.864332Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_wc_admin_notes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.865115Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_wc_admin_notes` because it could not be opened.
2025-06-10T12:22:15.865519Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.865795Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.866086Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.866477Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_wc_category_lookup.ibd' OS error: 103
2025-06-10T12:22:15.866921Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.867257Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.867664Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_wc_category_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.868699Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_wc_category_lookup` because it could not be opened.
2025-06-10T12:22:15.869975Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.870235Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.870671Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.871165Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_wc_customer_lookup.ibd' OS error: 103
2025-06-10T12:22:15.871558Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.871833Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.872315Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_wc_customer_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.872924Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_wc_customer_lookup` because it could not be opened.
2025-06-10T12:22:15.873375Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.873640Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.873910Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.874514Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_wc_download_log.ibd' OS error: 103
2025-06-10T12:22:15.875009Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.875567Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.876487Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_wc_download_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.877680Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_wc_download_log` because it could not be opened.
2025-06-10T12:22:15.878583Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.879003Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.879511Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.879955Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_wc_order_coupon_lookup.ibd' OS error: 103
2025-06-10T12:22:15.880348Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.880594Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.880979Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_wc_order_coupon_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.881643Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_wc_order_coupon_lookup` because it could not be opened.
2025-06-10T12:22:15.882079Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.882448Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.882703Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.883077Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_wc_order_product_lookup.ibd' OS error: 103
2025-06-10T12:22:15.883564Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.883815Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.884284Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_wc_order_product_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.884989Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_wc_order_product_lookup` because it could not be opened.
2025-06-10T12:22:15.885527Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.885784Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.886131Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.886509Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_wc_order_stats.ibd' OS error: 103
2025-06-10T12:22:15.886826Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.887220Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.887784Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_wc_order_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.888477Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_wc_order_stats` because it could not be opened.
2025-06-10T12:22:15.888908Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.889277Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.889583Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.889977Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_wc_order_tax_lookup.ibd' OS error: 103
2025-06-10T12:22:15.890400Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.890651Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.891122Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_wc_order_tax_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.891689Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_wc_order_tax_lookup` because it could not be opened.
2025-06-10T12:22:15.892233Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.892504Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.892764Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.893314Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_wc_product_meta_lookup.ibd' OS error: 103
2025-06-10T12:22:15.893725Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.894159Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.894578Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_wc_product_meta_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.895248Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_wc_product_meta_lookup` because it could not be opened.
2025-06-10T12:22:15.895675Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.895932Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.896303Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.896739Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_wc_reserved_stock.ibd' OS error: 103
2025-06-10T12:22:15.897118Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.897388Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.897811Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_wc_reserved_stock`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.898436Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_wc_reserved_stock` because it could not be opened.
2025-06-10T12:22:15.899260Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.899521Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.900467Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.901268Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_wc_tax_rate_classes.ibd' OS error: 103
2025-06-10T12:22:15.901658Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.901920Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.902762Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_wc_tax_rate_classes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.903452Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_wc_tax_rate_classes` because it could not be opened.
2025-06-10T12:22:15.904128Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.904582Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.904934Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.905410Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_wc_webhooks.ibd' OS error: 103
2025-06-10T12:22:15.905753Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.906051Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.906606Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_wc_webhooks`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.907420Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_wc_webhooks` because it could not be opened.
2025-06-10T12:22:15.907936Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.908211Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.908520Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.908909Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_woocommerce_api_keys.ibd' OS error: 103
2025-06-10T12:22:15.909293Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.909617Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.910060Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_woocommerce_api_keys`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.910752Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_woocommerce_api_keys` because it could not be opened.
2025-06-10T12:22:15.911225Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.911667Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.911953Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.912417Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_woocommerce_attribute_taxonomies.ibd' OS error: 103
2025-06-10T12:22:15.912809Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.913057Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.913730Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_woocommerce_attribute_taxonomies`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.914384Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_woocommerce_attribute_taxonomies` because it could not be opened.
2025-06-10T12:22:15.914860Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.915130Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.915430Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.915812Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_woocommerce_downloadable_product_permissions.ibd' OS error: 103
2025-06-10T12:22:15.916221Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.916503Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.916917Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_woocommerce_downloadable_product_permissions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.917605Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_woocommerce_downloadable_product_permissions` because it could not be opened.
2025-06-10T12:22:15.918078Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.918373Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.918639Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.919015Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_woocommerce_log.ibd' OS error: 103
2025-06-10T12:22:15.919387Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.919783Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.920274Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_woocommerce_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.920921Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_woocommerce_log` because it could not be opened.
2025-06-10T12:22:15.921398Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.921709Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.921970Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.922399Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_woocommerce_order_itemmeta.ibd' OS error: 103
2025-06-10T12:22:15.922749Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.923043Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.923548Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_woocommerce_order_itemmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.924124Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_woocommerce_order_itemmeta` because it could not be opened.
2025-06-10T12:22:15.924599Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.924853Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.925111Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.925674Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_woocommerce_order_items.ibd' OS error: 103
2025-06-10T12:22:15.926082Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.926382Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.926776Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_woocommerce_order_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.927444Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_woocommerce_order_items` because it could not be opened.
2025-06-10T12:22:15.927843Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.928097Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.928491Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.928854Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_woocommerce_payment_tokenmeta.ibd' OS error: 103
2025-06-10T12:22:15.929270Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.929536Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.929929Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_woocommerce_payment_tokenmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.930645Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_woocommerce_payment_tokenmeta` because it could not be opened.
2025-06-10T12:22:15.931057Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.931430Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.931816Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.932485Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_woocommerce_payment_tokens.ibd' OS error: 103
2025-06-10T12:22:15.933713Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.933982Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.934545Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_woocommerce_payment_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.935627Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_woocommerce_payment_tokens` because it could not be opened.
2025-06-10T12:22:15.936117Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.936451Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.936728Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.937113Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_woocommerce_sessions.ibd' OS error: 103
2025-06-10T12:22:15.937582Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.937842Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.938323Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_woocommerce_sessions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.938932Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_woocommerce_sessions` because it could not be opened.
2025-06-10T12:22:15.939596Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.939940Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.940256Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.940638Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_woocommerce_shipping_zone_locations.ibd' OS error: 103
2025-06-10T12:22:15.941024Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.941399Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.941860Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_woocommerce_shipping_zone_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.942513Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_woocommerce_shipping_zone_locations` because it could not be opened.
2025-06-10T12:22:15.943013Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.943308Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.943584Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.943951Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_woocommerce_shipping_zone_methods.ibd' OS error: 103
2025-06-10T12:22:15.944509Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.944802Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.945281Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_woocommerce_shipping_zone_methods`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.946081Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_woocommerce_shipping_zone_methods` because it could not be opened.
2025-06-10T12:22:15.946620Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.946997Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.947283Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.947756Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_woocommerce_shipping_zones.ibd' OS error: 103
2025-06-10T12:22:15.948667Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.949544Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.949982Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_woocommerce_shipping_zones`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.950698Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_woocommerce_shipping_zones` because it could not be opened.
2025-06-10T12:22:15.951274Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.951808Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.952165Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.952750Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_woocommerce_tax_rate_locations.ibd' OS error: 103
2025-06-10T12:22:15.953168Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.953438Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.953916Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_woocommerce_tax_rate_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.954599Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_woocommerce_tax_rate_locations` because it could not be opened.
2025-06-10T12:22:15.955099Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.955362Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.955693Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.956081Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_woocommerce_tax_rates.ibd' OS error: 103
2025-06-10T12:22:15.956444Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.956765Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.957176Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_woocommerce_tax_rates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.957834Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_woocommerce_tax_rates` because it could not be opened.
2025-06-10T12:22:15.958320Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.958729Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.959048Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.959458Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:15.959861Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.960129Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.960596Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.961183Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:15.961689Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.961960Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.962217Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.962628Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:15.963184Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.963458Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.963971Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.964597Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:15.965051Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.965318Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.965619Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.966007Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:15.966338Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.966694Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.967192Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.967832Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:15.968226Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.968480Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.968828Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.969193Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb1\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:15.969610Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.969887Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.970287Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb1/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.970966Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb1/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:15.971414Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.971792Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.972054Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.972459Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_actionscheduler_actions.ibd' OS error: 103
2025-06-10T12:22:15.972936Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.973394Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.973951Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_actionscheduler_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.974740Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_actionscheduler_actions` because it could not be opened.
2025-06-10T12:22:15.975194Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.975451Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.975804Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.976168Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_actionscheduler_claims.ibd' OS error: 103
2025-06-10T12:22:15.976547Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.976830Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.977222Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_actionscheduler_claims`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.977930Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_actionscheduler_claims` because it could not be opened.
2025-06-10T12:22:15.978375Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.979008Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.979632Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.980343Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_actionscheduler_groups.ibd' OS error: 103
2025-06-10T12:22:15.981085Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.981526Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.982045Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_actionscheduler_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.982730Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_actionscheduler_groups` because it could not be opened.
2025-06-10T12:22:15.983416Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.983775Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.984091Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.984501Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_actionscheduler_logs.ibd' OS error: 103
2025-06-10T12:22:15.984974Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.985346Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.985763Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_actionscheduler_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.986465Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_actionscheduler_logs` because it could not be opened.
2025-06-10T12:22:15.986901Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.987261Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.987527Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.987898Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:15.988410Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.988962Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.989485Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.990203Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:15.990906Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.991286Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.991616Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.992104Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_comments.ibd' OS error: 103
2025-06-10T12:22:15.992452Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.992725Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.993179Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.993845Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_comments` because it could not be opened.
2025-06-10T12:22:15.994417Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.994709Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.995143Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.995531Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:15.995850Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.996144Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.996576Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:15.997193Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_fbv` because it could not be opened.
2025-06-10T12:22:15.997594Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:15.997861Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:15.998153Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:15.998542Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:15.998901Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:15.999195Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:15.999712Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.000365Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:16.000792Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.001320Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.001587Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.002009Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_links.ibd' OS error: 103
2025-06-10T12:22:16.002485Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.002875Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.003550Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.004433Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_links` because it could not be opened.
2025-06-10T12:22:16.005362Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.005701Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.006090Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.006714Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_options.ibd' OS error: 103
2025-06-10T12:22:16.007324Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.007658Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.008144Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.008682Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_options` because it could not be opened.
2025-06-10T12:22:16.009142Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.009429Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.009698Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.010102Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_post_views.ibd' OS error: 103
2025-06-10T12:22:16.010435Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.010695Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.011185Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_post_views`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.011742Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_post_views` because it could not be opened.
2025-06-10T12:22:16.012380Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.013173Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.013495Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.013946Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:16.014410Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.014675Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.015564Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.016243Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_postmeta` because it could not be opened.
2025-06-10T12:22:16.017035Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.017338Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.017658Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.018099Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_posts.ibd' OS error: 103
2025-06-10T12:22:16.018457Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.018755Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.019228Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.019792Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_posts` because it could not be opened.
2025-06-10T12:22:16.020269Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.020539Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.020860Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.021260Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_revslider_css.ibd' OS error: 103
2025-06-10T12:22:16.021601Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.021939Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.022361Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_revslider_css`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.023035Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_revslider_css` because it could not be opened.
2025-06-10T12:22:16.023696Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.024014Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.024291Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.024674Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_revslider_css_bkp.ibd' OS error: 103
2025-06-10T12:22:16.025098Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.025364Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.025770Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_revslider_css_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.026446Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_revslider_css_bkp` because it could not be opened.
2025-06-10T12:22:16.026961Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.027322Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.027600Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.028000Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_revslider_layer_animations.ibd' OS error: 103
2025-06-10T12:22:16.028373Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.028676Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.029122Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_revslider_layer_animations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.029731Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_revslider_layer_animations` because it could not be opened.
2025-06-10T12:22:16.030229Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.030498Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.030770Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.031190Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_revslider_layer_animations_bkp.ibd' OS error: 103
2025-06-10T12:22:16.031569Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.031878Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.032299Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_revslider_layer_animations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.032950Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_revslider_layer_animations_bkp` because it could not be opened.
2025-06-10T12:22:16.033397Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.033761Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.034086Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.034464Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_revslider_navigations.ibd' OS error: 103
2025-06-10T12:22:16.034875Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.035175Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.035568Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_revslider_navigations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.036368Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_revslider_navigations` because it could not be opened.
2025-06-10T12:22:16.036967Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.037260Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.037595Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.038104Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_revslider_navigations_bkp.ibd' OS error: 103
2025-06-10T12:22:16.038446Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.038691Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.039234Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_revslider_navigations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.039871Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_revslider_navigations_bkp` because it could not be opened.
2025-06-10T12:22:16.040318Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.040584Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.040899Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.041283Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_revslider_sliders.ibd' OS error: 103
2025-06-10T12:22:16.041626Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.041925Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.042336Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_revslider_sliders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.044598Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_revslider_sliders` because it could not be opened.
2025-06-10T12:22:16.045113Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.045955Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.046866Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.047275Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_revslider_sliders_bkp.ibd' OS error: 103
2025-06-10T12:22:16.047775Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.048116Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.048649Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_revslider_sliders_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.049407Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_revslider_sliders_bkp` because it could not be opened.
2025-06-10T12:22:16.049910Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.050175Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.050507Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.050898Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_revslider_slides.ibd' OS error: 103
2025-06-10T12:22:16.051248Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.051734Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.052176Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_revslider_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.052965Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_revslider_slides` because it could not be opened.
2025-06-10T12:22:16.053777Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.054059Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.054441Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.054835Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_revslider_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:16.055176Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.055511Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.055911Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_revslider_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.056583Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_revslider_slides_bkp` because it could not be opened.
2025-06-10T12:22:16.056999Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.057286Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.057595Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.057972Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_revslider_static_slides.ibd' OS error: 103
2025-06-10T12:22:16.058476Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.058729Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.059107Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_revslider_static_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.059803Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_revslider_static_slides` because it could not be opened.
2025-06-10T12:22:16.060432Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.060754Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.061009Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.061470Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_revslider_static_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:16.061862Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.062109Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.062563Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_revslider_static_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.063148Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_revslider_static_slides_bkp` because it could not be opened.
2025-06-10T12:22:16.063659Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.063904Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.064153Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.064757Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_sbi_instagram_feeds_posts.ibd' OS error: 103
2025-06-10T12:22:16.065134Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.065517Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.065908Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_sbi_instagram_feeds_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.066529Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_sbi_instagram_feeds_posts` because it could not be opened.
2025-06-10T12:22:16.066957Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.067214Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.067537Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.067938Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_sbi_instagram_posts.ibd' OS error: 103
2025-06-10T12:22:16.068397Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.068658Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.069083Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_sbi_instagram_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.070026Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_sbi_instagram_posts` because it could not be opened.
2025-06-10T12:22:16.070543Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.070837Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.071108Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.071608Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:16.072159Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.072482Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.072904Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.073520Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:16.074328Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.074599Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.075087Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.076596Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:16.077082Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.077428Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.077904Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.078892Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:16.079387Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.079873Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.080177Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.080606Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:16.080939Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.081203Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.081665Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.082259Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_termmeta` because it could not be opened.
2025-06-10T12:22:16.082731Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.083001Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.083279Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.083704Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_terms.ibd' OS error: 103
2025-06-10T12:22:16.084037Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.084304Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.084777Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.085352Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_terms` because it could not be opened.
2025-06-10T12:22:16.085803Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.086069Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.086342Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.086753Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:16.087080Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.087345Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.087787Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.088355Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_usermeta` because it could not be opened.
2025-06-10T12:22:16.088770Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.089035Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.089303Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.089715Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_users.ibd' OS error: 103
2025-06-10T12:22:16.090033Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.090294Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.090734Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.091289Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_users` because it could not be opened.
2025-06-10T12:22:16.091710Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.091979Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.092326Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.092904Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_wc_admin_note_actions.ibd' OS error: 103
2025-06-10T12:22:16.093301Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.093635Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.094035Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_wc_admin_note_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.094668Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_wc_admin_note_actions` because it could not be opened.
2025-06-10T12:22:16.095113Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.095392Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.095682Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.096069Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_wc_admin_notes.ibd' OS error: 103
2025-06-10T12:22:16.096453Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.096722Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.097137Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_wc_admin_notes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.097778Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_wc_admin_notes` because it could not be opened.
2025-06-10T12:22:16.098185Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.098479Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.098922Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.099348Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_wc_category_lookup.ibd' OS error: 103
2025-06-10T12:22:16.099763Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.100032Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.100496Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_wc_category_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.101106Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_wc_category_lookup` because it could not be opened.
2025-06-10T12:22:16.101624Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.101877Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.102134Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.102638Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_wc_customer_lookup.ibd' OS error: 103
2025-06-10T12:22:16.102989Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.103247Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.103707Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_wc_customer_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.104292Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_wc_customer_lookup` because it could not be opened.
2025-06-10T12:22:16.104721Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.105042Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.105339Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.105823Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_wc_download_log.ibd' OS error: 103
2025-06-10T12:22:16.106583Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.106840Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.107688Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_wc_download_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.108624Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_wc_download_log` because it could not be opened.
2025-06-10T12:22:16.109178Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.110063Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.110336Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.110828Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_wc_order_coupon_lookup.ibd' OS error: 103
2025-06-10T12:22:16.111219Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.111485Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.111970Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_wc_order_coupon_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.112637Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_wc_order_coupon_lookup` because it could not be opened.
2025-06-10T12:22:16.113155Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.113428Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.113764Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.114149Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_wc_order_product_lookup.ibd' OS error: 103
2025-06-10T12:22:16.114512Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.114836Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.115262Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_wc_order_product_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.115942Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_wc_order_product_lookup` because it could not be opened.
2025-06-10T12:22:16.116407Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.116744Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.117018Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.117413Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_wc_order_stats.ibd' OS error: 103
2025-06-10T12:22:16.117818Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.118084Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.118497Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_wc_order_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.119142Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_wc_order_stats` because it could not be opened.
2025-06-10T12:22:16.119607Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.119876Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.120147Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.120586Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_wc_order_tax_lookup.ibd' OS error: 103
2025-06-10T12:22:16.120944Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.121203Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.121672Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_wc_order_tax_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.122252Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_wc_order_tax_lookup` because it could not be opened.
2025-06-10T12:22:16.122749Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.123008Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.123275Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.123762Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_wc_product_meta_lookup.ibd' OS error: 103
2025-06-10T12:22:16.124123Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.124381Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.124856Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_wc_product_meta_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.125443Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_wc_product_meta_lookup` because it could not be opened.
2025-06-10T12:22:16.125964Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.126227Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.126565Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.126951Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_wc_reserved_stock.ibd' OS error: 103
2025-06-10T12:22:16.127298Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.127624Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.128034Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_wc_reserved_stock`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.128687Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_wc_reserved_stock` because it could not be opened.
2025-06-10T12:22:16.129088Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.129349Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.129690Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.130092Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_wc_tax_rate_classes.ibd' OS error: 103
2025-06-10T12:22:16.130444Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.130756Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.131165Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_wc_tax_rate_classes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.131817Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_wc_tax_rate_classes` because it could not be opened.
2025-06-10T12:22:16.132222Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.132547Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.132822Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.133204Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_wc_webhooks.ibd' OS error: 103
2025-06-10T12:22:16.133603Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.133865Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.134410Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_wc_webhooks`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.135054Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_wc_webhooks` because it could not be opened.
2025-06-10T12:22:16.135434Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.135787Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.136056Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.136433Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_woocommerce_api_keys.ibd' OS error: 103
2025-06-10T12:22:16.136848Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.137109Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.137567Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_woocommerce_api_keys`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.138159Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_woocommerce_api_keys` because it could not be opened.
2025-06-10T12:22:16.138627Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.138889Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.139158Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.139596Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_woocommerce_attribute_taxonomies.ibd' OS error: 103
2025-06-10T12:22:16.139974Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.140233Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.140697Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_woocommerce_attribute_taxonomies`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.141351Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_woocommerce_attribute_taxonomies` because it could not be opened.
2025-06-10T12:22:16.141898Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.142220Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.142571Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.142959Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_woocommerce_downloadable_product_permissions.ibd' OS error: 103
2025-06-10T12:22:16.143362Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.143683Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.144092Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_woocommerce_downloadable_product_permissions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.144797Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_woocommerce_downloadable_product_permissions` because it could not be opened.
2025-06-10T12:22:16.145255Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.145614Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.145898Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.146275Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_woocommerce_log.ibd' OS error: 103
2025-06-10T12:22:16.146677Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.146938Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.147349Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_woocommerce_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.147991Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_woocommerce_log` because it could not be opened.
2025-06-10T12:22:16.148518Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.148803Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.149076Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.149517Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_woocommerce_order_itemmeta.ibd' OS error: 103
2025-06-10T12:22:16.149981Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.150254Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.150738Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_woocommerce_order_itemmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.151381Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_woocommerce_order_itemmeta` because it could not be opened.
2025-06-10T12:22:16.151906Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.152199Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.152524Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.152903Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_woocommerce_order_items.ibd' OS error: 103
2025-06-10T12:22:16.153319Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.153640Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.154615Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_woocommerce_order_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.155643Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_woocommerce_order_items` because it could not be opened.
2025-06-10T12:22:16.156336Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.156708Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.156988Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.158104Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_woocommerce_payment_tokenmeta.ibd' OS error: 103
2025-06-10T12:22:16.158600Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.158904Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.159395Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_woocommerce_payment_tokenmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.160184Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_woocommerce_payment_tokenmeta` because it could not be opened.
2025-06-10T12:22:16.161032Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.161478Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.162006Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.162613Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_woocommerce_payment_tokens.ibd' OS error: 103
2025-06-10T12:22:16.163300Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.163873Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.164740Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_woocommerce_payment_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.165971Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_woocommerce_payment_tokens` because it could not be opened.
2025-06-10T12:22:16.166773Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.167165Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.167460Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.167899Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_woocommerce_sessions.ibd' OS error: 103
2025-06-10T12:22:16.168253Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.168570Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.168984Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_woocommerce_sessions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.169632Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_woocommerce_sessions` because it could not be opened.
2025-06-10T12:22:16.170060Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.170393Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.170708Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.171092Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_woocommerce_shipping_zone_locations.ibd' OS error: 103
2025-06-10T12:22:16.171582Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.171847Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.172257Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_woocommerce_shipping_zone_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.172920Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_woocommerce_shipping_zone_locations` because it could not be opened.
2025-06-10T12:22:16.173391Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.173703Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.173972Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.174331Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_woocommerce_shipping_zone_methods.ibd' OS error: 103
2025-06-10T12:22:16.174761Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.175063Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.175541Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_woocommerce_shipping_zone_methods`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.176173Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_woocommerce_shipping_zone_methods` because it could not be opened.
2025-06-10T12:22:16.176650Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.176917Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.177187Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.177597Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_woocommerce_shipping_zones.ibd' OS error: 103
2025-06-10T12:22:16.177969Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.178230Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.178671Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_woocommerce_shipping_zones`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.179278Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_woocommerce_shipping_zones` because it could not be opened.
2025-06-10T12:22:16.179735Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.180000Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.180271Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.180736Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_woocommerce_tax_rate_locations.ibd' OS error: 103
2025-06-10T12:22:16.181114Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.181375Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.181812Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_woocommerce_tax_rate_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.182470Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_woocommerce_tax_rate_locations` because it could not be opened.
2025-06-10T12:22:16.182993Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.183270Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.183628Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.183997Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_woocommerce_tax_rates.ibd' OS error: 103
2025-06-10T12:22:16.184346Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.184716Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.185125Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_woocommerce_tax_rates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.185772Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_woocommerce_tax_rates` because it could not be opened.
2025-06-10T12:22:16.186233Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.186510Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.187024Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.187546Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:16.188095Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.188981Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.189963Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.191077Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:16.191663Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.191997Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.192324Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.192719Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:16.193059Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.193544Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.194206Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.195273Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:16.196121Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.196651Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.197149Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.197969Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:16.198518Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.198957Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.199433Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.199993Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:16.200451Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.200713Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.200981Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.201377Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb2\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:16.201734Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.201993Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.202615Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb2/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.203253Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb2/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:16.203695Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.203961Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.204441Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.204829Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_actionscheduler_actions.ibd' OS error: 103
2025-06-10T12:22:16.205234Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.205503Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.205911Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_actionscheduler_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.206537Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_actionscheduler_actions` because it could not be opened.
2025-06-10T12:22:16.206961Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.207250Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.207517Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.207893Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_actionscheduler_claims.ibd' OS error: 103
2025-06-10T12:22:16.208275Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.208658Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.209079Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_actionscheduler_claims`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.209709Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_actionscheduler_claims` because it could not be opened.
2025-06-10T12:22:16.210117Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.210516Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.210828Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.211281Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_actionscheduler_groups.ibd' OS error: 103
2025-06-10T12:22:16.211650Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.211901Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.212397Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_actionscheduler_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.212970Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_actionscheduler_groups` because it could not be opened.
2025-06-10T12:22:16.213664Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.213954Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.214368Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.214748Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_actionscheduler_logs.ibd' OS error: 103
2025-06-10T12:22:16.215087Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.215383Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.215877Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_actionscheduler_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.216540Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_actionscheduler_logs` because it could not be opened.
2025-06-10T12:22:16.216938Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.217239Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.217511Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.217877Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:16.218242Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.218507Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.218923Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.219891Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:16.221088Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.221946Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.222225Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.222987Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_comments.ibd' OS error: 103
2025-06-10T12:22:16.223329Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.223655Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.224103Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.224734Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_comments` because it could not be opened.
2025-06-10T12:22:16.225136Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.225403Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.225721Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.226118Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:16.226440Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.226730Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.227145Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.227773Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_fbv` because it could not be opened.
2025-06-10T12:22:16.228229Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.228535Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.228816Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.229211Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:16.229609Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.229877Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.230308Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.231035Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:16.231557Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.231835Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.232107Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.232512Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_links.ibd' OS error: 103
2025-06-10T12:22:16.232857Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.233119Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.233564Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.234123Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_links` because it could not be opened.
2025-06-10T12:22:16.234531Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.234800Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.235070Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.235462Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_options.ibd' OS error: 103
2025-06-10T12:22:16.235817Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.236081Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.236526Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.237109Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_options` because it could not be opened.
2025-06-10T12:22:16.237481Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.237816Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.238076Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.238442Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:16.238846Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.239097Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.239532Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.240125Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_postmeta` because it could not be opened.
2025-06-10T12:22:16.240508Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.240848Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.241120Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.241556Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_posts.ibd' OS error: 103
2025-06-10T12:22:16.241887Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.242136Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.242637Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.243198Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_posts` because it could not be opened.
2025-06-10T12:22:16.243661Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.243980Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.244255Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.244707Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_revslider_css.ibd' OS error: 103
2025-06-10T12:22:16.245143Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.245467Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.246143Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_revslider_css`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.246909Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_revslider_css` because it could not be opened.
2025-06-10T12:22:16.247344Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.247721Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.247981Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.248340Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_revslider_css_bkp.ibd' OS error: 103
2025-06-10T12:22:16.248738Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.248989Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.249377Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_revslider_css_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.250219Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_revslider_css_bkp` because it could not be opened.
2025-06-10T12:22:16.251385Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.252139Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.252413Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.252889Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_revslider_layer_animations.ibd' OS error: 103
2025-06-10T12:22:16.253328Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.253628Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.254184Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_revslider_layer_animations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.255030Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_revslider_layer_animations` because it could not be opened.
2025-06-10T12:22:16.255780Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.256078Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.256366Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.256782Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_revslider_layer_animations_bkp.ibd' OS error: 103
2025-06-10T12:22:16.257154Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.257453Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.257870Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_revslider_layer_animations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.258599Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_revslider_layer_animations_bkp` because it could not be opened.
2025-06-10T12:22:16.259095Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.259368Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.259676Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.260060Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_revslider_navigations.ibd' OS error: 103
2025-06-10T12:22:16.260457Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.260758Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.261213Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_revslider_navigations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.261883Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_revslider_navigations` because it could not be opened.
2025-06-10T12:22:16.262355Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.262693Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.262970Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.263405Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_revslider_navigations_bkp.ibd' OS error: 103
2025-06-10T12:22:16.263871Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.264138Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.264608Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_revslider_navigations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.265199Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_revslider_navigations_bkp` because it could not be opened.
2025-06-10T12:22:16.265680Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.265942Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.266209Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.266628Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_revslider_sliders.ibd' OS error: 103
2025-06-10T12:22:16.266973Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.267235Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.267684Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_revslider_sliders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.268257Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_revslider_sliders` because it could not be opened.
2025-06-10T12:22:16.268942Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.269225Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.269624Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.270051Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_revslider_sliders_bkp.ibd' OS error: 103
2025-06-10T12:22:16.270442Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.270710Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.271135Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_revslider_sliders_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.271758Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_revslider_sliders_bkp` because it could not be opened.
2025-06-10T12:22:16.272189Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.272490Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.272755Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.273128Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_revslider_slides.ibd' OS error: 103
2025-06-10T12:22:16.273521Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.273785Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.274252Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_revslider_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.274878Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_revslider_slides` because it could not be opened.
2025-06-10T12:22:16.275279Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.275579Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.275901Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.276320Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_revslider_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:16.276758Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.277022Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.277501Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_revslider_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.278081Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_revslider_slides_bkp` because it could not be opened.
2025-06-10T12:22:16.278598Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.278890Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.279170Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.279591Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_revslider_static_slides.ibd' OS error: 103
2025-06-10T12:22:16.279957Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.280222Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.280686Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_revslider_static_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.281288Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_revslider_static_slides` because it could not be opened.
2025-06-10T12:22:16.281755Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.282022Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.282417Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.282849Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_revslider_static_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:16.284143Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.284920Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.286423Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_revslider_static_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.287349Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_revslider_static_slides_bkp` because it could not be opened.
2025-06-10T12:22:16.287915Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.288340Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.288698Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.289126Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_sbi_instagram_feed_locator.ibd' OS error: 103
2025-06-10T12:22:16.289509Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.289771Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.290260Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_sbi_instagram_feed_locator`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.290918Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_sbi_instagram_feed_locator` because it could not be opened.
2025-06-10T12:22:16.291408Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.291675Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.291998Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.292391Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_sbi_instagram_feeds_posts.ibd' OS error: 103
2025-06-10T12:22:16.292760Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.293107Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.293562Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_sbi_instagram_feeds_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.294315Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_sbi_instagram_feeds_posts` because it could not be opened.
2025-06-10T12:22:16.294863Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.295220Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.295489Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.295901Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_sbi_instagram_posts.ibd' OS error: 103
2025-06-10T12:22:16.296258Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.296518Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.296951Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_sbi_instagram_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.297540Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_sbi_instagram_posts` because it could not be opened.
2025-06-10T12:22:16.297990Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.298251Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.298518Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.298940Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:16.299543Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.299870Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.300297Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.300939Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:16.301690Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.302010Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.302290Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.302674Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:16.303046Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.303310Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.303721Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.304321Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:16.304715Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.305008Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.305296Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.305788Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:16.306137Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.306407Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.306859Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.307435Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_termmeta` because it could not be opened.
2025-06-10T12:22:16.307864Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.308147Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.308422Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.308858Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_terms.ibd' OS error: 103
2025-06-10T12:22:16.309183Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.309440Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.309890Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.310518Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_terms` because it could not be opened.
2025-06-10T12:22:16.310962Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.311291Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.311559Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.311978Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:16.312304Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.312565Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.313010Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.313636Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_usermeta` because it could not be opened.
2025-06-10T12:22:16.314286Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.315137Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.315406Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.316653Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_users.ibd' OS error: 103
2025-06-10T12:22:16.318090Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.318368Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.318864Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.319492Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_users` because it could not be opened.
2025-06-10T12:22:16.319934Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.320200Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.320472Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.320896Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_wc_admin_note_actions.ibd' OS error: 103
2025-06-10T12:22:16.321250Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.321510Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.321975Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_wc_admin_note_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.322598Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_wc_admin_note_actions` because it could not be opened.
2025-06-10T12:22:16.323146Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.323411Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.323760Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.324143Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_wc_admin_notes.ibd' OS error: 103
2025-06-10T12:22:16.324543Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.324924Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.325472Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_wc_admin_notes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.326158Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_wc_admin_notes` because it could not be opened.
2025-06-10T12:22:16.326648Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.326922Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.327196Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.327607Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_wc_category_lookup.ibd' OS error: 103
2025-06-10T12:22:16.327968Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.328227Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.328679Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_wc_category_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.329277Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_wc_category_lookup` because it could not be opened.
2025-06-10T12:22:16.329702Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.329973Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.330245Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.330668Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_wc_customer_lookup.ibd' OS error: 103
2025-06-10T12:22:16.331022Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.331286Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.331739Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_wc_customer_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.332329Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_wc_customer_lookup` because it could not be opened.
2025-06-10T12:22:16.332764Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.333028Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.333300Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.333712Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_wc_download_log.ibd' OS error: 103
2025-06-10T12:22:16.334069Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.334327Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.334769Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_wc_download_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.335486Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_wc_download_log` because it could not be opened.
2025-06-10T12:22:16.335903Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.336168Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.336439Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.336852Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_wc_order_coupon_lookup.ibd' OS error: 103
2025-06-10T12:22:16.337211Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.337473Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.337918Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_wc_order_coupon_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.338523Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_wc_order_coupon_lookup` because it could not be opened.
2025-06-10T12:22:16.338966Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.339229Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.339498Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.339894Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_wc_order_product_lookup.ibd' OS error: 103
2025-06-10T12:22:16.340256Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.340529Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.340962Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_wc_order_product_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.341593Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_wc_order_product_lookup` because it could not be opened.
2025-06-10T12:22:16.342016Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.342280Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.342594Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.342981Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_wc_order_stats.ibd' OS error: 103
2025-06-10T12:22:16.343324Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.343616Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.344033Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_wc_order_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.344645Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_wc_order_stats` because it could not be opened.
2025-06-10T12:22:16.345039Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.345304Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.345605Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.345989Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_wc_order_tax_lookup.ibd' OS error: 103
2025-06-10T12:22:16.346339Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.346630Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.347042Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_wc_order_tax_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.347666Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_wc_order_tax_lookup` because it could not be opened.
2025-06-10T12:22:16.348063Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.348326Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.348622Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.349006Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_wc_product_meta_lookup.ibd' OS error: 103
2025-06-10T12:22:16.349371Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.349676Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.350087Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_wc_product_meta_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.350708Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_wc_product_meta_lookup` because it could not be opened.
2025-06-10T12:22:16.351101Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.351474Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.351830Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.352204Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_wc_reserved_stock.ibd' OS error: 103
2025-06-10T12:22:16.352672Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.352925Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.353320Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_wc_reserved_stock`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.353974Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_wc_reserved_stock` because it could not be opened.
2025-06-10T12:22:16.354372Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.354801Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.355087Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.355613Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_wc_tax_rate_classes.ibd' OS error: 103
2025-06-10T12:22:16.355983Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.356241Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.356935Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_wc_tax_rate_classes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.357742Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_wc_tax_rate_classes` because it could not be opened.
2025-06-10T12:22:16.358173Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.358420Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.358776Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.359142Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_wc_webhooks.ibd' OS error: 103
2025-06-10T12:22:16.359520Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.359837Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.360227Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_wc_webhooks`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.360858Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_wc_webhooks` because it could not be opened.
2025-06-10T12:22:16.361228Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.361625Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.361895Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.362359Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_woocommerce_api_keys.ibd' OS error: 103
2025-06-10T12:22:16.364162Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.365176Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.366547Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_woocommerce_api_keys`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.367217Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_woocommerce_api_keys` because it could not be opened.
2025-06-10T12:22:16.367698Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.368020Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.368295Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.368696Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_woocommerce_attribute_taxonomies.ibd' OS error: 103
2025-06-10T12:22:16.369074Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.369334Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.369816Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_woocommerce_attribute_taxonomies`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.370438Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_woocommerce_attribute_taxonomies` because it could not be opened.
2025-06-10T12:22:16.370950Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.371216Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.371540Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.371943Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_woocommerce_downloadable_product_permissions.ibd' OS error: 103
2025-06-10T12:22:16.372352Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.372706Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.373324Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_woocommerce_downloadable_product_permissions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.374054Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_woocommerce_downloadable_product_permissions` because it could not be opened.
2025-06-10T12:22:16.374649Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.375145Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.375442Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.375853Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_woocommerce_log.ibd' OS error: 103
2025-06-10T12:22:16.376245Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.376569Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.376998Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_woocommerce_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.377630Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_woocommerce_log` because it could not be opened.
2025-06-10T12:22:16.378064Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.378334Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.378635Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.379014Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_woocommerce_order_itemmeta.ibd' OS error: 103
2025-06-10T12:22:16.379381Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.379798Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.380255Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_woocommerce_order_itemmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.380986Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_woocommerce_order_itemmeta` because it could not be opened.
2025-06-10T12:22:16.381553Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.381827Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.382085Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.382480Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_woocommerce_order_items.ibd' OS error: 103
2025-06-10T12:22:16.382881Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.383128Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.383575Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_woocommerce_order_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.384153Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_woocommerce_order_items` because it could not be opened.
2025-06-10T12:22:16.384631Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.384894Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.385150Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.385604Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_woocommerce_payment_tokenmeta.ibd' OS error: 103
2025-06-10T12:22:16.386081Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.386352Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.386838Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_woocommerce_payment_tokenmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.387490Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_woocommerce_payment_tokenmeta` because it could not be opened.
2025-06-10T12:22:16.387954Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.388225Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.388583Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.388974Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_woocommerce_payment_tokens.ibd' OS error: 103
2025-06-10T12:22:16.389344Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.389680Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.390084Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_woocommerce_payment_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.390758Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_woocommerce_payment_tokens` because it could not be opened.
2025-06-10T12:22:16.391185Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.391504Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.391848Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.392205Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_woocommerce_sessions.ibd' OS error: 103
2025-06-10T12:22:16.392622Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.392880Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.393277Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_woocommerce_sessions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.393917Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_woocommerce_sessions` because it could not be opened.
2025-06-10T12:22:16.395050Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.395879Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.396527Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.396905Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_woocommerce_shipping_zone_locations.ibd' OS error: 103
2025-06-10T12:22:16.397626Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.397993Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.398437Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_woocommerce_shipping_zone_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.399105Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_woocommerce_shipping_zone_locations` because it could not be opened.
2025-06-10T12:22:16.399650Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.399938Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.400227Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.400610Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_woocommerce_shipping_zone_methods.ibd' OS error: 103
2025-06-10T12:22:16.401200Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.401469Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.401875Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_woocommerce_shipping_zone_methods`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.402528Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_woocommerce_shipping_zone_methods` because it could not be opened.
2025-06-10T12:22:16.403108Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.403389Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.403659Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.404097Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_woocommerce_shipping_zones.ibd' OS error: 103
2025-06-10T12:22:16.404477Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.404750Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.405278Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_woocommerce_shipping_zones`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.406011Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_woocommerce_shipping_zones` because it could not be opened.
2025-06-10T12:22:16.406577Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.406919Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.407208Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.407632Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_woocommerce_tax_rate_locations.ibd' OS error: 103
2025-06-10T12:22:16.408076Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.408355Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.408781Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_woocommerce_tax_rate_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.409437Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_woocommerce_tax_rate_locations` because it could not be opened.
2025-06-10T12:22:16.409922Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.410207Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.410479Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.410863Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_woocommerce_tax_rates.ibd' OS error: 103
2025-06-10T12:22:16.411249Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.411511Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.411965Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_woocommerce_tax_rates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.412561Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_woocommerce_tax_rates` because it could not be opened.
2025-06-10T12:22:16.413000Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.413314Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.413631Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.414073Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:16.414571Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.414846Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.415295Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.415930Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:16.416342Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.416609Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.416895Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.417302Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:16.417637Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.417935Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.418357Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.418976Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:16.419368Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.419634Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.419967Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.420426Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:16.420903Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.421237Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.421646Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.422429Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:16.422846Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.423165Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.423425Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.423794Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_asiapcb3\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:16.424245Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.424491Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.424945Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_asiapcb3/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.425588Z 0 [Warning] InnoDB: Ignoring tablespace `client_asiapcb3/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:16.426328Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.426750Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.427039Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.427730Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove1\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:16.428139Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.428402Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.428863Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove1/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.429439Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove1/wp_fbv` because it could not be opened.
2025-06-10T12:22:16.429930Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.430194Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.430591Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.430995Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove1\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:16.431551Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.431854Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.432271Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove1/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.432889Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove1/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:16.433347Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.433636Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.434073Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.434534Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove1\wp_wfls_2fa_secrets.ibd' OS error: 103
2025-06-10T12:22:16.434869Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.435183Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.435764Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove1/wp_wfls_2fa_secrets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.436436Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove1/wp_wfls_2fa_secrets` because it could not be opened.
2025-06-10T12:22:16.436954Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.437231Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.437526Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.437910Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove1\wp_wfls_settings.ibd' OS error: 103
2025-06-10T12:22:16.438266Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.438587Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.439030Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove1/wp_wfls_settings`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.439635Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove1/wp_wfls_settings` because it could not be opened.
2025-06-10T12:22:16.440079Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.440486Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.440761Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.441119Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_actionscheduler_actions.ibd' OS error: 103
2025-06-10T12:22:16.441576Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.441869Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.442300Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_actionscheduler_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.442943Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_actionscheduler_actions` because it could not be opened.
2025-06-10T12:22:16.443433Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.443791Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.444049Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.444488Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_actionscheduler_claims.ibd' OS error: 103
2025-06-10T12:22:16.444845Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.445096Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.445577Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_actionscheduler_claims`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.446138Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_actionscheduler_claims` because it could not be opened.
2025-06-10T12:22:16.446662Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.446942Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.447204Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.447688Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_actionscheduler_groups.ibd' OS error: 103
2025-06-10T12:22:16.448030Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.448339Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.448740Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_actionscheduler_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.449361Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_actionscheduler_groups` because it could not be opened.
2025-06-10T12:22:16.449774Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.450027Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.450363Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.450772Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_actionscheduler_logs.ibd' OS error: 103
2025-06-10T12:22:16.451123Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.451497Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.451981Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_actionscheduler_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.452810Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_actionscheduler_logs` because it could not be opened.
2025-06-10T12:22:16.453555Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.453813Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.454071Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.454499Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_brizy_logs.ibd' OS error: 103
2025-06-10T12:22:16.454818Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.455065Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.455574Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_brizy_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.456154Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_brizy_logs` because it could not be opened.
2025-06-10T12:22:16.456628Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.456878Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.457133Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.457556Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:16.457872Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.458148Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.458636Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.459550Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:16.459988Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.460582Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.460853Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.461414Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_comments.ibd' OS error: 103
2025-06-10T12:22:16.461938Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.462206Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.463147Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.463783Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_comments` because it could not be opened.
2025-06-10T12:22:16.464339Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.464628Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.465086Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.465475Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_evf_entries.ibd' OS error: 103
2025-06-10T12:22:16.465832Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.466104Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.466526Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_evf_entries`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.467235Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_evf_entries` because it could not be opened.
2025-06-10T12:22:16.467745Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.468025Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.468292Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.468739Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_evf_entrymeta.ibd' OS error: 103
2025-06-10T12:22:16.469167Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.469437Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.469932Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_evf_entrymeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.470611Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_evf_entrymeta` because it could not be opened.
2025-06-10T12:22:16.471101Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.471416Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.471748Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.472120Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_evf_sessions.ibd' OS error: 103
2025-06-10T12:22:16.472556Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.472867Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.473264Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_evf_sessions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.473907Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_evf_sessions` because it could not be opened.
2025-06-10T12:22:16.474536Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.474867Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.475126Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.475501Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:16.475889Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.476139Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.476583Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.477118Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_fbv` because it could not be opened.
2025-06-10T12:22:16.477463Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.477900Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.478161Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.478654Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:16.478994Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.479284Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.479734Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.480295Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:16.480931Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.481190Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.481444Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.482034Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_links.ibd' OS error: 103
2025-06-10T12:22:16.482340Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.482692Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.483144Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.483755Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_links` because it could not be opened.
2025-06-10T12:22:16.484138Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.484453Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.484882Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.485319Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_options.ibd' OS error: 103
2025-06-10T12:22:16.485755Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.486139Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.486586Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.487133Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_options` because it could not be opened.
2025-06-10T12:22:16.487674Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.487924Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.488175Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.488615Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_post_views.ibd' OS error: 103
2025-06-10T12:22:16.488933Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.489177Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.489688Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_post_views`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.490292Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_post_views` because it could not be opened.
2025-06-10T12:22:16.491947Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.493405Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.493754Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.494583Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:16.495273Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.495618Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.496049Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.496698Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_postmeta` because it could not be opened.
2025-06-10T12:22:16.497104Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.497423Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.497760Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.498226Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_posts.ibd' OS error: 103
2025-06-10T12:22:16.498615Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.498916Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.499304Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.499909Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_posts` because it could not be opened.
2025-06-10T12:22:16.500312Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.500620Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.500896Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.501263Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_strong_views.ibd' OS error: 103
2025-06-10T12:22:16.501653Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.501928Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.502331Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_strong_views`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.503320Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_strong_views` because it could not be opened.
2025-06-10T12:22:16.503887Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.504144Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.504405Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.504872Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:16.505205Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.505453Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.505913Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.506468Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:16.506951Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.507198Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.507452Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.507914Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:16.508232Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.508475Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.508971Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.509592Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:16.510003Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.510326Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.510688Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.511108Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:16.511436Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.511735Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.512157Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.512793Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_termmeta` because it could not be opened.
2025-06-10T12:22:16.513156Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.513405Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.513741Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.514128Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_terms.ibd' OS error: 103
2025-06-10T12:22:16.514516Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.514818Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.515214Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.515892Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_terms` because it could not be opened.
2025-06-10T12:22:16.516314Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.516671Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.516939Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.517376Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:16.517769Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.518043Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.518474Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.519064Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_usermeta` because it could not be opened.
2025-06-10T12:22:16.519479Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.519760Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.520028Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.520409Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_users.ibd' OS error: 103
2025-06-10T12:22:16.520762Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.521024Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.521631Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.522205Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_users` because it could not be opened.
2025-06-10T12:22:16.522795Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.523559Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.523830Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.524602Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_wc_admin_note_actions.ibd' OS error: 103
2025-06-10T12:22:16.524969Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.525717Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.526349Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_wc_admin_note_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.527035Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_wc_admin_note_actions` because it could not be opened.
2025-06-10T12:22:16.527548Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.527829Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.528103Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.528514Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_wc_admin_notes.ibd' OS error: 103
2025-06-10T12:22:16.528878Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.529378Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.529862Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_wc_admin_notes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.530668Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_wc_admin_notes` because it could not be opened.
2025-06-10T12:22:16.531247Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.531509Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.532038Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.532418Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_wc_category_lookup.ibd' OS error: 103
2025-06-10T12:22:16.532753Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.533179Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.533631Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_wc_category_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.534319Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_wc_category_lookup` because it could not be opened.
2025-06-10T12:22:16.534754Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.535104Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.535379Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.535740Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_wc_customer_lookup.ibd' OS error: 103
2025-06-10T12:22:16.536235Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.536693Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.537202Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_wc_customer_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.537938Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_wc_customer_lookup` because it could not be opened.
2025-06-10T12:22:16.538370Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.538624Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.538967Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.539394Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_wc_download_log.ibd' OS error: 103
2025-06-10T12:22:16.539786Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.540061Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.540475Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_wc_download_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.541093Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_wc_download_log` because it could not be opened.
2025-06-10T12:22:16.541509Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.541787Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.542086Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.542452Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_wc_order_coupon_lookup.ibd' OS error: 103
2025-06-10T12:22:16.542834Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.543138Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.543535Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_wc_order_coupon_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.544183Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_wc_order_coupon_lookup` because it could not be opened.
2025-06-10T12:22:16.544623Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.544928Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.545188Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.545585Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_wc_order_product_lookup.ibd' OS error: 103
2025-06-10T12:22:16.546054Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.546372Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.546814Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_wc_order_product_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.547407Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_wc_order_product_lookup` because it could not be opened.
2025-06-10T12:22:16.547899Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.548163Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.548423Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.548841Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_wc_order_stats.ibd' OS error: 103
2025-06-10T12:22:16.549184Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.549437Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.549935Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_wc_order_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.550490Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_wc_order_stats` because it could not be opened.
2025-06-10T12:22:16.550991Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.551321Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.551638Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.552205Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_wc_order_tax_lookup.ibd' OS error: 103
2025-06-10T12:22:16.552606Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.552950Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.553378Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_wc_order_tax_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.554034Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_wc_order_tax_lookup` because it could not be opened.
2025-06-10T12:22:16.554436Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.554689Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.555024Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.555520Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_wc_product_meta_lookup.ibd' OS error: 103
2025-06-10T12:22:16.556137Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.556411Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.556867Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_wc_product_meta_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.557502Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_wc_product_meta_lookup` because it could not be opened.
2025-06-10T12:22:16.557980Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.558247Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.558520Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.558932Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_wc_reserved_stock.ibd' OS error: 103
2025-06-10T12:22:16.559284Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.559548Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.559989Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_wc_reserved_stock`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.560576Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_wc_reserved_stock` because it could not be opened.
2025-06-10T12:22:16.561059Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.561327Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.561582Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.562057Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_wc_tax_rate_classes.ibd' OS error: 103
2025-06-10T12:22:16.562406Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.562656Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.563110Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_wc_tax_rate_classes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.563732Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_wc_tax_rate_classes` because it could not be opened.
2025-06-10T12:22:16.564528Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.565059Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.565356Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.565811Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_wc_webhooks.ibd' OS error: 103
2025-06-10T12:22:16.566173Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.566443Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.566934Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_wc_webhooks`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.567455Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_wc_webhooks` because it could not be opened.
2025-06-10T12:22:16.567945Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.568192Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.568510Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.569005Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_woocommerce_api_keys.ibd' OS error: 103
2025-06-10T12:22:16.569382Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.569915Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.570340Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_woocommerce_api_keys`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.571510Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_woocommerce_api_keys` because it could not be opened.
2025-06-10T12:22:16.572013Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.572369Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.572672Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.573073Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_woocommerce_attribute_taxonomies.ibd' OS error: 103
2025-06-10T12:22:16.573653Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.573912Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.574405Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_woocommerce_attribute_taxonomies`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.575499Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_woocommerce_attribute_taxonomies` because it could not be opened.
2025-06-10T12:22:16.576070Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.576360Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.576633Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.577074Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_woocommerce_downloadable_product_permissions.ibd' OS error: 103
2025-06-10T12:22:16.577511Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.577827Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.578226Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_woocommerce_downloadable_product_permissions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.578942Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_woocommerce_downloadable_product_permissions` because it could not be opened.
2025-06-10T12:22:16.579494Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.579870Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.580160Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.580533Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_woocommerce_log.ibd' OS error: 103
2025-06-10T12:22:16.580974Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.581229Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.581632Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_woocommerce_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.582282Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_woocommerce_log` because it could not be opened.
2025-06-10T12:22:16.582882Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.583170Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.583431Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.584089Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_woocommerce_order_itemmeta.ibd' OS error: 103
2025-06-10T12:22:16.584458Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.584804Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.585251Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_woocommerce_order_itemmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.585899Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_woocommerce_order_itemmeta` because it could not be opened.
2025-06-10T12:22:16.586330Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.586594Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.586918Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.587267Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_woocommerce_order_items.ibd' OS error: 103
2025-06-10T12:22:16.587595Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.588034Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.588423Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_woocommerce_order_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.589174Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_woocommerce_order_items` because it could not be opened.
2025-06-10T12:22:16.589620Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.589991Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.590419Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.591115Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_woocommerce_payment_tokenmeta.ibd' OS error: 103
2025-06-10T12:22:16.591486Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.591796Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.592202Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_woocommerce_payment_tokenmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.592890Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_woocommerce_payment_tokenmeta` because it could not be opened.
2025-06-10T12:22:16.593403Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.593758Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.594057Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.594490Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_woocommerce_payment_tokens.ibd' OS error: 103
2025-06-10T12:22:16.594946Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.595298Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.595752Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_woocommerce_payment_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.596751Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_woocommerce_payment_tokens` because it could not be opened.
2025-06-10T12:22:16.597257Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.597521Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.597833Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.598211Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_woocommerce_sessions.ibd' OS error: 103
2025-06-10T12:22:16.598564Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.598850Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.599260Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_woocommerce_sessions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.599894Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_woocommerce_sessions` because it could not be opened.
2025-06-10T12:22:16.600304Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.600572Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.600873Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.601247Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_woocommerce_shipping_zone_locations.ibd' OS error: 103
2025-06-10T12:22:16.601642Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.601920Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.602323Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_woocommerce_shipping_zone_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.603852Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_woocommerce_shipping_zone_locations` because it could not be opened.
2025-06-10T12:22:16.605305Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.606520Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.606994Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.607544Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_woocommerce_shipping_zone_methods.ibd' OS error: 103
2025-06-10T12:22:16.608016Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.608312Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.608747Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_woocommerce_shipping_zone_methods`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.609468Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_woocommerce_shipping_zone_methods` because it could not be opened.
2025-06-10T12:22:16.610175Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.610682Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.610960Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.611442Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_woocommerce_shipping_zones.ibd' OS error: 103
2025-06-10T12:22:16.611856Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.612186Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.612680Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_woocommerce_shipping_zones`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.613383Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_woocommerce_shipping_zones` because it could not be opened.
2025-06-10T12:22:16.613884Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.614182Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.614518Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.614897Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_woocommerce_tax_rate_locations.ibd' OS error: 103
2025-06-10T12:22:16.615335Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.615591Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.615998Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_woocommerce_tax_rate_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.616634Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_woocommerce_tax_rate_locations` because it could not be opened.
2025-06-10T12:22:16.617082Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.617376Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.617662Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.618040Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_woocommerce_tax_rates.ibd' OS error: 103
2025-06-10T12:22:16.618423Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.618680Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.619084Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_woocommerce_tax_rates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.619693Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_woocommerce_tax_rates` because it could not be opened.
2025-06-10T12:22:16.620101Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.620387Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.620653Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.621025Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:16.621403Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.621656Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.622058Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.622682Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:16.623075Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.623388Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.623663Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.624046Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:16.624407Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.624666Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.625073Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.625670Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:16.626055Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.626354Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.626621Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.627000Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:16.627357Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.627616Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.628026Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.628619Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:16.629068Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.629358Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.629635Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.630015Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_beelove2\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:16.630400Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.630660Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.631068Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_beelove2/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.631680Z 0 [Warning] InnoDB: Ignoring tablespace `client_beelove2/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:16.632413Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.632697Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.632966Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.633474Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_actionscheduler_actions.ibd' OS error: 103
2025-06-10T12:22:16.633818Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.634066Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.634674Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_actionscheduler_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.635361Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_actionscheduler_actions` because it could not be opened.
2025-06-10T12:22:16.636121Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.636387Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.636728Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.637102Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_actionscheduler_claims.ibd' OS error: 103
2025-06-10T12:22:16.637525Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.637830Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.638254Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_actionscheduler_claims`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.639225Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_actionscheduler_claims` because it could not be opened.
2025-06-10T12:22:16.639731Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.640035Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.640310Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.640706Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_actionscheduler_groups.ibd' OS error: 103
2025-06-10T12:22:16.641081Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.641345Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.641779Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_actionscheduler_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.642372Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_actionscheduler_groups` because it could not be opened.
2025-06-10T12:22:16.642868Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.643132Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.643405Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.643936Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_actionscheduler_logs.ibd' OS error: 103
2025-06-10T12:22:16.644315Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.644733Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.645190Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_actionscheduler_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.645854Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_actionscheduler_logs` because it could not be opened.
2025-06-10T12:22:16.646316Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.646730Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.646997Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.647466Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:16.647815Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.648063Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.648506Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.649077Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:16.649506Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.649807Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.650069Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.650477Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_comments.ibd' OS error: 103
2025-06-10T12:22:16.650817Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.651059Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.651492Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.652296Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_comments` because it could not be opened.
2025-06-10T12:22:16.652785Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.653029Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.653281Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.653731Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:16.654057Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.654323Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.654801Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.655357Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_fbv` because it could not be opened.
2025-06-10T12:22:16.655785Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.656052Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.656323Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.656736Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:16.657090Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.657353Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.657801Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.658406Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:16.658850Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.659116Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.659386Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.659875Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_links.ibd' OS error: 103
2025-06-10T12:22:16.660245Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.660710Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.661106Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.661708Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_links` because it could not be opened.
2025-06-10T12:22:16.662097Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.662383Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.662789Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.663308Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_newsletter.ibd' OS error: 103
2025-06-10T12:22:16.663770Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.664070Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.664523Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_newsletter`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.665091Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_newsletter` because it could not be opened.
2025-06-10T12:22:16.665547Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.665807Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.666065Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.666599Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_newsletter_emails.ibd' OS error: 103
2025-06-10T12:22:16.667039Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.667296Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.668138Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_newsletter_emails`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.668952Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_newsletter_emails` because it could not be opened.
2025-06-10T12:22:16.669596Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.669862Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.670394Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.671069Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_newsletter_sent.ibd' OS error: 103
2025-06-10T12:22:16.671405Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.671716Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.672159Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_newsletter_sent`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.672732Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_newsletter_sent` because it could not be opened.
2025-06-10T12:22:16.673241Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.673498Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.673754Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.674197Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_newsletter_stats.ibd' OS error: 103
2025-06-10T12:22:16.674536Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.674785Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.675319Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_newsletter_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.675994Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_newsletter_stats` because it could not be opened.
2025-06-10T12:22:16.676516Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.676775Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.677157Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.677546Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_newsletter_user_logs.ibd' OS error: 103
2025-06-10T12:22:16.677886Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.678213Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.678608Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_newsletter_user_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.679255Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_newsletter_user_logs` because it could not be opened.
2025-06-10T12:22:16.679669Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.679918Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.680270Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.680630Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_ngg_album.ibd' OS error: 103
2025-06-10T12:22:16.680947Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.681288Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.681678Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_ngg_album`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.682270Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_ngg_album` because it could not be opened.
2025-06-10T12:22:16.682628Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.682876Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.683225Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.683706Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_ngg_gallery.ibd' OS error: 103
2025-06-10T12:22:16.684125Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.684394Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.684796Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_ngg_gallery`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.685515Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_ngg_gallery` because it could not be opened.
2025-06-10T12:22:16.685937Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.686251Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.686526Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.686907Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_ngg_pictures.ibd' OS error: 103
2025-06-10T12:22:16.687261Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.687523Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.687945Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_ngg_pictures`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.688523Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_ngg_pictures` because it could not be opened.
2025-06-10T12:22:16.688905Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.689192Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.689460Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.689838Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_options.ibd' OS error: 103
2025-06-10T12:22:16.690208Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.690469Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.690879Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.691461Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_options` because it could not be opened.
2025-06-10T12:22:16.691829Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.692114Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.692382Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.692783Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_post_views.ibd' OS error: 103
2025-06-10T12:22:16.693131Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.693401Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.693814Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_post_views`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.694395Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_post_views` because it could not be opened.
2025-06-10T12:22:16.694780Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.695075Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.695394Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.695805Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:16.696204Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.696466Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.696880Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.697561Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_postmeta` because it could not be opened.
2025-06-10T12:22:16.698044Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.698318Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.698635Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.699107Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_posts.ibd' OS error: 103
2025-06-10T12:22:16.699481Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.699826Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.700285Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.700927Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_posts` because it could not be opened.
2025-06-10T12:22:16.701417Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.701686Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.702062Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.702559Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_revslider_css.ibd' OS error: 103
2025-06-10T12:22:16.703137Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.703514Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.703986Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_revslider_css`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.704620Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_revslider_css` because it could not be opened.
2025-06-10T12:22:16.705085Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.705468Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.705798Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.706158Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_revslider_css_bkp.ibd' OS error: 103
2025-06-10T12:22:16.706551Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.706800Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.707249Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_revslider_css_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.707887Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_revslider_css_bkp` because it could not be opened.
2025-06-10T12:22:16.708436Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.708755Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.709016Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.709504Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_revslider_layer_animations.ibd' OS error: 103
2025-06-10T12:22:16.710011Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.710354Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.710813Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_revslider_layer_animations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.711459Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_revslider_layer_animations` because it could not be opened.
2025-06-10T12:22:16.711915Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.712164Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.712489Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.712854Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_revslider_layer_animations_bkp.ibd' OS error: 103
2025-06-10T12:22:16.713208Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.713546Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.713936Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_revslider_layer_animations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.714607Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_revslider_layer_animations_bkp` because it could not be opened.
2025-06-10T12:22:16.715010Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.715346Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.715618Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.715970Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_revslider_navigations.ibd' OS error: 103
2025-06-10T12:22:16.716389Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.716757Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.717177Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_revslider_navigations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.717854Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_revslider_navigations` because it could not be opened.
2025-06-10T12:22:16.718345Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.718690Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.718952Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.719485Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_revslider_navigations_bkp.ibd' OS error: 103
2025-06-10T12:22:16.720001Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.720301Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.720768Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_revslider_navigations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.721410Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_revslider_navigations_bkp` because it could not be opened.
2025-06-10T12:22:16.721824Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.722069Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.722410Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.722896Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_revslider_sliders.ibd' OS error: 103
2025-06-10T12:22:16.723469Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.723723Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.724156Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_revslider_sliders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.724829Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_revslider_sliders` because it could not be opened.
2025-06-10T12:22:16.725271Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.725591Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.725839Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.726216Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_revslider_sliders_bkp.ibd' OS error: 103
2025-06-10T12:22:16.726640Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.726884Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.727330Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_revslider_sliders_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.727895Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_revslider_sliders_bkp` because it could not be opened.
2025-06-10T12:22:16.728332Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.728610Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.728859Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.729289Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_revslider_slides.ibd' OS error: 103
2025-06-10T12:22:16.729725Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.730035Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.730903Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_revslider_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.731682Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_revslider_slides` because it could not be opened.
2025-06-10T12:22:16.732153Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.732429Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.733235Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.733618Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_revslider_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:16.733986Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.734287Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.735122Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_revslider_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.735859Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_revslider_slides_bkp` because it could not be opened.
2025-06-10T12:22:16.736376Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.736654Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.736948Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.737440Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_revslider_static_slides.ibd' OS error: 103
2025-06-10T12:22:16.737848Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.738119Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.738566Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_revslider_static_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.739163Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_revslider_static_slides` because it could not be opened.
2025-06-10T12:22:16.739680Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.739950Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.740227Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.740689Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_revslider_static_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:16.741048Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.741301Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.741773Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_revslider_static_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.742431Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_revslider_static_slides_bkp` because it could not be opened.
2025-06-10T12:22:16.742914Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.743175Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.743531Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.744028Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_sbi_instagram_feeds_posts.ibd' OS error: 103
2025-06-10T12:22:16.744465Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.744740Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.745156Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_sbi_instagram_feeds_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.745787Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_sbi_instagram_feeds_posts` because it could not be opened.
2025-06-10T12:22:16.746247Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.746559Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.746830Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.747211Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_sbi_instagram_posts.ibd' OS error: 103
2025-06-10T12:22:16.747584Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.747845Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.748257Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_sbi_instagram_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.748877Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_sbi_instagram_posts` because it could not be opened.
2025-06-10T12:22:16.749321Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.749596Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.749863Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.750242Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:16.750801Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.751074Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.751582Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.752154Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:16.752680Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.752936Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.753195Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.753652Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:16.753972Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.754223Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.754756Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.755387Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:16.755798Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.756053Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.756405Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.756784Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:16.757126Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.757476Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.757938Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.758569Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_termmeta` because it could not be opened.
2025-06-10T12:22:16.758998Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.759261Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.759644Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.760043Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_terms.ibd' OS error: 103
2025-06-10T12:22:16.760607Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.760857Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.761281Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.761876Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_terms` because it could not be opened.
2025-06-10T12:22:16.762235Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.762584Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.762839Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.763373Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:16.763739Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.763993Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.764456Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.765082Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_usermeta` because it could not be opened.
2025-06-10T12:22:16.765591Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.765848Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.766116Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.766555Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_users.ibd' OS error: 103
2025-06-10T12:22:16.766859Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.767104Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.767571Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.768092Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_users` because it could not be opened.
2025-06-10T12:22:16.768538Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.768833Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.769155Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.769825Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_wc_admin_note_actions.ibd' OS error: 103
2025-06-10T12:22:16.770186Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.770489Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.770884Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_wc_admin_note_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.771580Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_wc_admin_note_actions` because it could not be opened.
2025-06-10T12:22:16.771995Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.772307Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.772684Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.773092Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_wc_admin_notes.ibd' OS error: 103
2025-06-10T12:22:16.773452Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.773714Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.774128Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_wc_admin_notes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.774741Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_wc_admin_notes` because it could not be opened.
2025-06-10T12:22:16.775145Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.775435Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.775708Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.776093Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_wc_category_lookup.ibd' OS error: 103
2025-06-10T12:22:16.776514Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.776761Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.777156Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_wc_category_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.777851Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_wc_category_lookup` because it could not be opened.
2025-06-10T12:22:16.778411Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.778773Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.779091Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.780567Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_wc_customer_lookup.ibd' OS error: 103
2025-06-10T12:22:16.781502Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.781794Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.782709Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_wc_customer_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.783439Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_wc_customer_lookup` because it could not be opened.
2025-06-10T12:22:16.784012Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.784288Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.784578Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.784988Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_wc_download_log.ibd' OS error: 103
2025-06-10T12:22:16.785412Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.785686Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.786146Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_wc_download_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.786757Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_wc_download_log` because it could not be opened.
2025-06-10T12:22:16.787254Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.787525Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.787811Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.788480Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_wc_order_coupon_lookup.ibd' OS error: 103
2025-06-10T12:22:16.788833Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.789193Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.789594Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_wc_order_coupon_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.790265Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_wc_order_coupon_lookup` because it could not be opened.
2025-06-10T12:22:16.790744Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.791057Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.791394Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.791755Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_wc_order_product_lookup.ibd' OS error: 103
2025-06-10T12:22:16.792427Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.792703Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.793264Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_wc_order_product_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.793815Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_wc_order_product_lookup` because it could not be opened.
2025-06-10T12:22:16.794403Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.794651Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.794902Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.795559Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_wc_order_stats.ibd' OS error: 103
2025-06-10T12:22:16.796072Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.796405Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.797004Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_wc_order_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.797716Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_wc_order_stats` because it could not be opened.
2025-06-10T12:22:16.798242Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.798506Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.798774Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.799198Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_wc_order_tax_lookup.ibd' OS error: 103
2025-06-10T12:22:16.799545Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.799802Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.800289Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_wc_order_tax_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.800966Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_wc_order_tax_lookup` because it could not be opened.
2025-06-10T12:22:16.801377Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.801635Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.801932Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.802345Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_wc_product_meta_lookup.ibd' OS error: 103
2025-06-10T12:22:16.802697Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.803002Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.803415Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_wc_product_meta_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.804048Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_wc_product_meta_lookup` because it could not be opened.
2025-06-10T12:22:16.804508Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.804777Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.805281Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.805729Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_wc_reserved_stock.ibd' OS error: 103
2025-06-10T12:22:16.806148Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.806413Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.806810Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_wc_reserved_stock`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.807453Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_wc_reserved_stock` because it could not be opened.
2025-06-10T12:22:16.807859Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.808204Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.808493Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.808973Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_wc_tax_rate_classes.ibd' OS error: 103
2025-06-10T12:22:16.809327Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.809577Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.810091Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_wc_tax_rate_classes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.811093Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_wc_tax_rate_classes` because it could not be opened.
2025-06-10T12:22:16.811576Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.812079Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.812548Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.813416Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_wc_webhooks.ibd' OS error: 103
2025-06-10T12:22:16.813760Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.814105Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.814519Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_wc_webhooks`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.815212Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_wc_webhooks` because it could not be opened.
2025-06-10T12:22:16.815656Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.815935Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.816232Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.816628Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_woocommerce_api_keys.ibd' OS error: 103
2025-06-10T12:22:16.816974Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.817275Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.817708Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_woocommerce_api_keys`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.818332Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_woocommerce_api_keys` because it could not be opened.
2025-06-10T12:22:16.818755Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.819026Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.819334Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.819728Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_woocommerce_attribute_taxonomies.ibd' OS error: 103
2025-06-10T12:22:16.820114Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.820445Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.820864Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_woocommerce_attribute_taxonomies`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.821547Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_woocommerce_attribute_taxonomies` because it could not be opened.
2025-06-10T12:22:16.822038Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.822380Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.822661Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.823171Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_woocommerce_downloadable_product_permissions.ibd' OS error: 103
2025-06-10T12:22:16.823683Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.823939Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.824494Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_woocommerce_downloadable_product_permissions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.825090Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_woocommerce_downloadable_product_permissions` because it could not be opened.
2025-06-10T12:22:16.825733Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.825987Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.826366Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.826808Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_woocommerce_log.ibd' OS error: 103
2025-06-10T12:22:16.827237Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.827545Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.828007Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_woocommerce_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.828648Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_woocommerce_log` because it could not be opened.
2025-06-10T12:22:16.829084Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.829386Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.829653Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.830029Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_woocommerce_order_itemmeta.ibd' OS error: 103
2025-06-10T12:22:16.830426Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.830687Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.831100Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_woocommerce_order_itemmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.831742Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_woocommerce_order_itemmeta` because it could not be opened.
2025-06-10T12:22:16.832197Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.832480Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.832748Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.833129Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_woocommerce_order_items.ibd' OS error: 103
2025-06-10T12:22:16.833516Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.833777Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.834214Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_woocommerce_order_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.834845Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_woocommerce_order_items` because it could not be opened.
2025-06-10T12:22:16.835311Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.835576Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.835848Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.836261Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_woocommerce_payment_tokenmeta.ibd' OS error: 103
2025-06-10T12:22:16.836632Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.836918Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.837359Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_woocommerce_payment_tokenmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.838150Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_woocommerce_payment_tokenmeta` because it could not be opened.
2025-06-10T12:22:16.838655Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.838919Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.839278Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.839712Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_woocommerce_payment_tokens.ibd' OS error: 103
2025-06-10T12:22:16.840059Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.840421Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.840814Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_woocommerce_payment_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.841511Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_woocommerce_payment_tokens` because it could not be opened.
2025-06-10T12:22:16.841955Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.842325Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.842698Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.843078Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_woocommerce_sessions.ibd' OS error: 103
2025-06-10T12:22:16.843524Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.843997Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.845107Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_woocommerce_sessions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.846737Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_woocommerce_sessions` because it could not be opened.
2025-06-10T12:22:16.847839Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.848182Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.848616Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.849071Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_woocommerce_shipping_zone_locations.ibd' OS error: 103
2025-06-10T12:22:16.849530Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.849792Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.850212Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_woocommerce_shipping_zone_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.850877Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_woocommerce_shipping_zone_locations` because it could not be opened.
2025-06-10T12:22:16.851418Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.851697Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.851971Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.852394Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_woocommerce_shipping_zone_methods.ibd' OS error: 103
2025-06-10T12:22:16.852780Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.853055Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.853548Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_woocommerce_shipping_zone_methods`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.854196Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_woocommerce_shipping_zone_methods` because it could not be opened.
2025-06-10T12:22:16.854917Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.855221Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.855582Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.855941Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_woocommerce_shipping_zones.ibd' OS error: 103
2025-06-10T12:22:16.856284Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.856638Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.857024Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_woocommerce_shipping_zones`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.857703Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_woocommerce_shipping_zones` because it could not be opened.
2025-06-10T12:22:16.858175Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.858691Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.858976Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.859438Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_woocommerce_tax_rate_locations.ibd' OS error: 103
2025-06-10T12:22:16.859925Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.860168Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.860648Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_woocommerce_tax_rate_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.861256Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_woocommerce_tax_rate_locations` because it could not be opened.
2025-06-10T12:22:16.861809Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.862064Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.862375Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.862800Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_woocommerce_tax_rates.ibd' OS error: 103
2025-06-10T12:22:16.863131Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.863480Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.863946Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_woocommerce_tax_rates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.864616Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_woocommerce_tax_rates` because it could not be opened.
2025-06-10T12:22:16.865109Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.865436Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.865709Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.866072Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:16.866551Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.866820Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.867233Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.867885Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:16.868356Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.868629Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.868901Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.869334Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:16.869676Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.869936Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.870397Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.871017Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:16.871529Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.871782Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.872041Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.872499Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:16.872895Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.873137Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.873646Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.874283Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:16.874787Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.875228Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.875616Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.876034Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:16.876721Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.876982Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.877550Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.878223Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:16.879099Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.879381Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.879816Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.880234Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_yith_wcwl.ibd' OS error: 103
2025-06-10T12:22:16.880557Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.880881Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.881299Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_yith_wcwl`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.881961Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_yith_wcwl` because it could not be opened.
2025-06-10T12:22:16.882391Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.882710Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.882979Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.883361Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_yith_wcwl_lists.ibd' OS error: 103
2025-06-10T12:22:16.883747Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.884009Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.884431Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_yith_wcwl_lists`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.885097Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_yith_wcwl_lists` because it could not be opened.
2025-06-10T12:22:16.885535Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.885865Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.886144Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.886549Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_yoast_indexable.ibd' OS error: 103
2025-06-10T12:22:16.886984Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.887326Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.887841Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_yoast_indexable`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.888506Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_yoast_indexable` because it could not be opened.
2025-06-10T12:22:16.888994Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.889266Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.889536Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.889978Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_yoast_indexable_hierarchy.ibd' OS error: 103
2025-06-10T12:22:16.890339Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.890670Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.891218Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_yoast_indexable_hierarchy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.891869Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_yoast_indexable_hierarchy` because it could not be opened.
2025-06-10T12:22:16.892353Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.892726Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.893026Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.893385Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_yoast_migrations.ibd' OS error: 103
2025-06-10T12:22:16.894089Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.894443Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.894946Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_yoast_migrations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.895497Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_yoast_migrations` because it could not be opened.
2025-06-10T12:22:16.896060Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.896359Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.896761Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.897130Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_yoast_primary_term.ibd' OS error: 103
2025-06-10T12:22:16.897464Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.897811Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.898244Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_yoast_primary_term`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.898880Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_yoast_primary_term` because it could not be opened.
2025-06-10T12:22:16.899290Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.899546Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.900025Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.900513Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri\wp_yoast_seo_links.ibd' OS error: 103
2025-06-10T12:22:16.901000Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.901380Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.901942Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri/wp_yoast_seo_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.902521Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri/wp_yoast_seo_links` because it could not be opened.
2025-06-10T12:22:16.902995Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.903269Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.903542Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.903953Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_actionscheduler_actions.ibd' OS error: 103
2025-06-10T12:22:16.904314Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.904611Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.905083Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_actionscheduler_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.905825Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_actionscheduler_actions` because it could not be opened.
2025-06-10T12:22:16.906283Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.906537Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.906984Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.907700Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_actionscheduler_claims.ibd' OS error: 103
2025-06-10T12:22:16.908041Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.908504Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.908932Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_actionscheduler_claims`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.909901Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_actionscheduler_claims` because it could not be opened.
2025-06-10T12:22:16.910879Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.911144Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.911448Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.911938Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_actionscheduler_groups.ibd' OS error: 103
2025-06-10T12:22:16.912326Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.912593Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.913068Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_actionscheduler_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.913665Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_actionscheduler_groups` because it could not be opened.
2025-06-10T12:22:16.914181Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.914445Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.914713Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.915156Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_actionscheduler_logs.ibd' OS error: 103
2025-06-10T12:22:16.915511Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.915770Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.916267Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_actionscheduler_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.916946Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_actionscheduler_logs` because it could not be opened.
2025-06-10T12:22:16.917428Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.917697Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.918052Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.918445Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:16.918795Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.919140Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.919607Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.920413Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:16.920887Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.921155Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.921424Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.921854Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_comments.ibd' OS error: 103
2025-06-10T12:22:16.922193Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.922453Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.922902Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.923463Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_comments` because it could not be opened.
2025-06-10T12:22:16.923879Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.924147Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.924417Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.924835Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:16.925165Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.925427Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.925884Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.926433Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_fbv` because it could not be opened.
2025-06-10T12:22:16.926839Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.927107Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.927377Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.927753Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:16.928239Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.928501Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.928943Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.929511Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:16.929973Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.930242Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.930501Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.930969Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_links.ibd' OS error: 103
2025-06-10T12:22:16.931276Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.931573Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.932091Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.932700Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_links` because it could not be opened.
2025-06-10T12:22:16.933309Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.933626Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.933937Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.934321Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_newsletter.ibd' OS error: 103
2025-06-10T12:22:16.934660Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.935002Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.935440Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_newsletter`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.936039Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_newsletter` because it could not be opened.
2025-06-10T12:22:16.936462Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.936859Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.937258Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.937902Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_newsletter_emails.ibd' OS error: 103
2025-06-10T12:22:16.938242Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.938487Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.939116Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_newsletter_emails`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.940268Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_newsletter_emails` because it could not be opened.
2025-06-10T12:22:16.941778Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.942359Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.942628Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.943109Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_newsletter_sent.ibd' OS error: 103
2025-06-10T12:22:16.943645Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.944205Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.944658Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_newsletter_sent`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.945339Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_newsletter_sent` because it could not be opened.
2025-06-10T12:22:16.945926Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.946237Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.946496Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.946863Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_newsletter_stats.ibd' OS error: 103
2025-06-10T12:22:16.947296Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.947548Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.948026Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_newsletter_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.948638Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_newsletter_stats` because it could not be opened.
2025-06-10T12:22:16.949125Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.949389Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.949805Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.950312Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_newsletter_user_logs.ibd' OS error: 103
2025-06-10T12:22:16.950697Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.951089Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.951533Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_newsletter_user_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.952178Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_newsletter_user_logs` because it could not be opened.
2025-06-10T12:22:16.952667Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.952980Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.953297Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.953657Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_ngg_album.ibd' OS error: 103
2025-06-10T12:22:16.954085Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.954350Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.954745Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_ngg_album`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.955347Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_ngg_album` because it could not be opened.
2025-06-10T12:22:16.955706Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.956014Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.956339Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.956907Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_ngg_gallery.ibd' OS error: 103
2025-06-10T12:22:16.957359Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.957629Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.958147Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_ngg_gallery`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.958774Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_ngg_gallery` because it could not be opened.
2025-06-10T12:22:16.959262Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.959516Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.959775Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.960233Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_ngg_pictures.ibd' OS error: 103
2025-06-10T12:22:16.960553Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.960805Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.961259Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_ngg_pictures`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.961810Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_ngg_pictures` because it could not be opened.
2025-06-10T12:22:16.962362Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.962758Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.963136Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.963526Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_options.ibd' OS error: 103
2025-06-10T12:22:16.963850Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.964140Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.964553Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.965141Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_options` because it could not be opened.
2025-06-10T12:22:16.965541Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.965826Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.966114Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.966509Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_post_views.ibd' OS error: 103
2025-06-10T12:22:16.966844Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.967130Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.967543Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_post_views`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.968145Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_post_views` because it could not be opened.
2025-06-10T12:22:16.968543Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.968805Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.969103Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.969481Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:16.969803Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.970100Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.970507Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.971083Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_postmeta` because it could not be opened.
2025-06-10T12:22:16.971458Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.971718Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.972025Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.972402Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_posts.ibd' OS error: 103
2025-06-10T12:22:16.972718Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.973000Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.973408Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.973977Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_posts` because it could not be opened.
2025-06-10T12:22:16.974339Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.974595Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.974876Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.975273Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_revslider_css.ibd' OS error: 103
2025-06-10T12:22:16.975732Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.976067Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.976464Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_revslider_css`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.977074Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_revslider_css` because it could not be opened.
2025-06-10T12:22:16.977453Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.977709Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.978028Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.978426Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_revslider_css_bkp.ibd' OS error: 103
2025-06-10T12:22:16.978762Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.979072Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.979469Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_revslider_css_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.980095Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_revslider_css_bkp` because it could not be opened.
2025-06-10T12:22:16.980518Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.980831Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.981121Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.981489Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_revslider_layer_animations.ibd' OS error: 103
2025-06-10T12:22:16.981883Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.982227Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.982624Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_revslider_layer_animations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.983529Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_revslider_layer_animations` because it could not be opened.
2025-06-10T12:22:16.984018Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.984304Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.984567Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.984995Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_revslider_layer_animations_bkp.ibd' OS error: 103
2025-06-10T12:22:16.985382Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.985628Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.986105Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_revslider_layer_animations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.987013Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_revslider_layer_animations_bkp` because it could not be opened.
2025-06-10T12:22:16.987694Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.987973Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.988490Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.989007Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_revslider_navigations.ibd' OS error: 103
2025-06-10T12:22:16.989487Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.989742Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.990276Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_revslider_navigations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.991354Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_revslider_navigations` because it could not be opened.
2025-06-10T12:22:16.991800Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.992125Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.992427Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.992820Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_revslider_navigations_bkp.ibd' OS error: 103
2025-06-10T12:22:16.993215Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.993473Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.993918Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_revslider_navigations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.994523Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_revslider_navigations_bkp` because it could not be opened.
2025-06-10T12:22:16.994997Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.995263Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.995537Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.995948Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_revslider_sliders.ibd' OS error: 103
2025-06-10T12:22:16.996294Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.996559Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:16.997035Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_revslider_sliders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:16.997617Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_revslider_sliders` because it could not be opened.
2025-06-10T12:22:16.998176Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:16.998482Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:16.998758Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:16.999171Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_revslider_sliders_bkp.ibd' OS error: 103
2025-06-10T12:22:16.999604Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:16.999958Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.000421Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_revslider_sliders_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.001092Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_revslider_sliders_bkp` because it could not be opened.
2025-06-10T12:22:17.001598Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.001902Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.002179Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.002584Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_revslider_slides.ibd' OS error: 103
2025-06-10T12:22:17.002949Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.003213Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.003630Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_revslider_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.004260Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_revslider_slides` because it could not be opened.
2025-06-10T12:22:17.004746Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.005061Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.005350Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.005741Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_revslider_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:17.006172Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.006436Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.006921Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_revslider_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.007509Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_revslider_slides_bkp` because it could not be opened.
2025-06-10T12:22:17.008014Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.008287Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.008557Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.009096Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_revslider_static_slides.ibd' OS error: 103
2025-06-10T12:22:17.009554Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.009847Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.010258Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_revslider_static_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.011003Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_revslider_static_slides` because it could not be opened.
2025-06-10T12:22:17.011502Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.011810Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.012090Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.012469Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_revslider_static_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:17.012871Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.013136Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.013551Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_revslider_static_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.014263Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_revslider_static_slides_bkp` because it could not be opened.
2025-06-10T12:22:17.014711Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.015036Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.015392Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.015834Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_sbi_instagram_feeds_posts.ibd' OS error: 103
2025-06-10T12:22:17.016206Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.016471Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.016966Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_sbi_instagram_feeds_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.017532Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_sbi_instagram_feeds_posts` because it could not be opened.
2025-06-10T12:22:17.018078Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.018331Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.018590Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.019083Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_sbi_instagram_posts.ibd' OS error: 103
2025-06-10T12:22:17.019435Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.019848Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.020460Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_sbi_instagram_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.021169Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_sbi_instagram_posts` because it could not be opened.
2025-06-10T12:22:17.021662Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.021983Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.022788Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.023211Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:17.023576Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.024297Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.024735Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.025398Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:17.026223Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.026533Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.026831Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.027451Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:17.027851Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.028168Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.028632Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.029254Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:17.029882Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.030143Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.030532Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.030915Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:17.031398Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.031712Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.032143Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.032816Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_termmeta` because it could not be opened.
2025-06-10T12:22:17.033375Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.033659Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.033983Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.034638Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_terms.ibd' OS error: 103
2025-06-10T12:22:17.034968Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.035280Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.035689Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.036463Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_terms` because it could not be opened.
2025-06-10T12:22:17.036887Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.037150Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.037478Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.037847Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:17.038194Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.038511Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.038970Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.039670Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_usermeta` because it could not be opened.
2025-06-10T12:22:17.040102Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.040414Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.040698Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.041075Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_users.ibd' OS error: 103
2025-06-10T12:22:17.041451Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.041698Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.042087Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.042715Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_users` because it could not be opened.
2025-06-10T12:22:17.043262Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.043601Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.043947Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.044399Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_wc_admin_note_actions.ibd' OS error: 103
2025-06-10T12:22:17.044761Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.045033Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.045638Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_wc_admin_note_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.046299Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_wc_admin_note_actions` because it could not be opened.
2025-06-10T12:22:17.046778Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.047053Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.047349Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.047737Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_wc_admin_notes.ibd' OS error: 103
2025-06-10T12:22:17.048079Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.048550Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.048969Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_wc_admin_notes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.049579Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_wc_admin_notes` because it could not be opened.
2025-06-10T12:22:17.050055Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.050385Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.050659Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.051060Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_wc_category_lookup.ibd' OS error: 103
2025-06-10T12:22:17.051466Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.051720Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.052127Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_wc_category_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.052744Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_wc_category_lookup` because it could not be opened.
2025-06-10T12:22:17.053182Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.053566Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.053830Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.054263Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_wc_customer_lookup.ibd' OS error: 103
2025-06-10T12:22:17.054601Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.054856Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.055356Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_wc_customer_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.055926Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_wc_customer_lookup` because it could not be opened.
2025-06-10T12:22:17.056903Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.057489Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.057771Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.058419Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_wc_download_log.ibd' OS error: 103
2025-06-10T12:22:17.058758Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.059018Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.059648Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_wc_download_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.060574Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_wc_download_log` because it could not be opened.
2025-06-10T12:22:17.061126Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.061560Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.061858Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.062378Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_wc_order_coupon_lookup.ibd' OS error: 103
2025-06-10T12:22:17.062746Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.063001Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.063541Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_wc_order_coupon_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.064128Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_wc_order_coupon_lookup` because it could not be opened.
2025-06-10T12:22:17.064768Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.065071Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.065431Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.065856Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_wc_order_product_lookup.ibd' OS error: 103
2025-06-10T12:22:17.066213Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.066534Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.066979Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_wc_order_product_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.067738Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_wc_order_product_lookup` because it could not be opened.
2025-06-10T12:22:17.068444Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.068782Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.069059Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.069476Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_wc_order_stats.ibd' OS error: 103
2025-06-10T12:22:17.069817Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.070135Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.070632Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_wc_order_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.071260Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_wc_order_stats` because it could not be opened.
2025-06-10T12:22:17.071734Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.072111Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.072439Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.072843Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_wc_order_tax_lookup.ibd' OS error: 103
2025-06-10T12:22:17.073203Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.073500Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.073918Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_wc_order_tax_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.074532Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_wc_order_tax_lookup` because it could not be opened.
2025-06-10T12:22:17.074987Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.075283Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.075652Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.076077Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_wc_product_meta_lookup.ibd' OS error: 103
2025-06-10T12:22:17.076507Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.076852Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.077358Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_wc_product_meta_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.077968Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_wc_product_meta_lookup` because it could not be opened.
2025-06-10T12:22:17.078454Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.078747Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.079092Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.079586Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_wc_reserved_stock.ibd' OS error: 103
2025-06-10T12:22:17.079932Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.080185Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.080671Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_wc_reserved_stock`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.081299Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_wc_reserved_stock` because it could not be opened.
2025-06-10T12:22:17.081737Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.081994Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.082347Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.082841Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_wc_tax_rate_classes.ibd' OS error: 103
2025-06-10T12:22:17.083687Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.084674Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.086092Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_wc_tax_rate_classes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.086961Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_wc_tax_rate_classes` because it could not be opened.
2025-06-10T12:22:17.087961Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.088276Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.088743Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.089254Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_wc_webhooks.ibd' OS error: 103
2025-06-10T12:22:17.089652Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.089969Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.090402Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_wc_webhooks`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.091018Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_wc_webhooks` because it could not be opened.
2025-06-10T12:22:17.091449Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.091718Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.092073Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.092531Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_woocommerce_api_keys.ibd' OS error: 103
2025-06-10T12:22:17.092967Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.093249Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.093674Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_woocommerce_api_keys`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.094334Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_woocommerce_api_keys` because it could not be opened.
2025-06-10T12:22:17.094792Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.095133Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.095417Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.095833Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_woocommerce_attribute_taxonomies.ibd' OS error: 103
2025-06-10T12:22:17.096254Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.096566Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.097024Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_woocommerce_attribute_taxonomies`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.097643Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_woocommerce_attribute_taxonomies` because it could not be opened.
2025-06-10T12:22:17.098143Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.098409Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.098678Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.099122Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_woocommerce_downloadable_product_permissions.ibd' OS error: 103
2025-06-10T12:22:17.099599Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.099886Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.100347Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_woocommerce_downloadable_product_permissions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.101155Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_woocommerce_downloadable_product_permissions` because it could not be opened.
2025-06-10T12:22:17.101701Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.102015Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.102295Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.102677Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_woocommerce_log.ibd' OS error: 103
2025-06-10T12:22:17.103057Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.103319Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.103737Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_woocommerce_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.104364Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_woocommerce_log` because it could not be opened.
2025-06-10T12:22:17.104791Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.105082Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.105354Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.105736Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_woocommerce_order_itemmeta.ibd' OS error: 103
2025-06-10T12:22:17.106163Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.106429Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.106855Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_woocommerce_order_itemmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.107471Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_woocommerce_order_itemmeta` because it could not be opened.
2025-06-10T12:22:17.107947Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.108254Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.108531Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.109044Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_woocommerce_order_items.ibd' OS error: 103
2025-06-10T12:22:17.109439Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.109692Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.110228Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_woocommerce_order_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.110799Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_woocommerce_order_items` because it could not be opened.
2025-06-10T12:22:17.111264Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.111517Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.111776Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.112220Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_woocommerce_payment_tokenmeta.ibd' OS error: 103
2025-06-10T12:22:17.112582Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.112995Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.113407Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_woocommerce_payment_tokenmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.114061Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_woocommerce_payment_tokenmeta` because it could not be opened.
2025-06-10T12:22:17.114513Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.115031Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.116491Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.116912Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_woocommerce_payment_tokens.ibd' OS error: 103
2025-06-10T12:22:17.117383Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.117662Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.118119Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_woocommerce_payment_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.119284Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_woocommerce_payment_tokens` because it could not be opened.
2025-06-10T12:22:17.120228Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.120518Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.120805Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.121212Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_woocommerce_sessions.ibd' OS error: 103
2025-06-10T12:22:17.121565Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.121842Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.122249Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_woocommerce_sessions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.122886Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_woocommerce_sessions` because it could not be opened.
2025-06-10T12:22:17.123370Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.123753Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.124322Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.125096Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_woocommerce_shipping_zone_locations.ibd' OS error: 103
2025-06-10T12:22:17.125831Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.126213Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.126957Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_woocommerce_shipping_zone_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.127869Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_woocommerce_shipping_zone_locations` because it could not be opened.
2025-06-10T12:22:17.128529Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.128900Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.129179Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.129578Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_woocommerce_shipping_zone_methods.ibd' OS error: 103
2025-06-10T12:22:17.130029Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.130286Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.130737Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_woocommerce_shipping_zone_methods`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.131345Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_woocommerce_shipping_zone_methods` because it could not be opened.
2025-06-10T12:22:17.131994Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.132261Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.132522Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.133036Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_woocommerce_shipping_zones.ibd' OS error: 103
2025-06-10T12:22:17.133389Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.133728Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.134158Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_woocommerce_shipping_zones`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.134819Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_woocommerce_shipping_zones` because it could not be opened.
2025-06-10T12:22:17.135252Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.135514Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.135902Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.136313Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_woocommerce_tax_rate_locations.ibd' OS error: 103
2025-06-10T12:22:17.136715Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.136983Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.137381Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_woocommerce_tax_rate_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.138057Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_woocommerce_tax_rate_locations` because it could not be opened.
2025-06-10T12:22:17.138557Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.138898Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.139241Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.139680Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_woocommerce_tax_rates.ibd' OS error: 103
2025-06-10T12:22:17.140052Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.140359Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.140933Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_woocommerce_tax_rates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.141731Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_woocommerce_tax_rates` because it could not be opened.
2025-06-10T12:22:17.142180Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.142440Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.142757Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.143136Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:17.143477Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.143795Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.144192Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.144858Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:17.145462Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.145822Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.146085Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.146444Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:17.146945Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.147198Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.147826Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.148488Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:17.149179Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.149840Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.150107Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.150577Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:17.151046Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.151599Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.152087Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.152865Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:17.153480Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.153885Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.154181Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.154610Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:17.155002Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.155283Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.155742Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.156352Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:17.157013Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.157299Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.157637Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.158049Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_yith_wcwl.ibd' OS error: 103
2025-06-10T12:22:17.158436Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.158752Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.159212Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_yith_wcwl`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.159831Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_yith_wcwl` because it could not be opened.
2025-06-10T12:22:17.160295Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.160586Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.160859Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.161221Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_yith_wcwl_lists.ibd' OS error: 103
2025-06-10T12:22:17.161652Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.161899Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.162292Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_yith_wcwl_lists`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.162911Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_yith_wcwl_lists` because it could not be opened.
2025-06-10T12:22:17.163294Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.163597Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.163870Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.164271Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_yoast_indexable.ibd' OS error: 103
2025-06-10T12:22:17.164720Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.165015Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.165409Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_yoast_indexable`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.166067Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_yoast_indexable` because it could not be opened.
2025-06-10T12:22:17.166708Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.167002Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.167273Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.167752Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_yoast_indexable_hierarchy.ibd' OS error: 103
2025-06-10T12:22:17.168108Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.168357Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.168802Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_yoast_indexable_hierarchy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.169379Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_yoast_indexable_hierarchy` because it could not be opened.
2025-06-10T12:22:17.170034Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.170289Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.170608Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.170978Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_yoast_migrations.ibd' OS error: 103
2025-06-10T12:22:17.171311Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.171659Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.172057Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_yoast_migrations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.172705Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_yoast_migrations` because it could not be opened.
2025-06-10T12:22:17.173083Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.173338Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.173662Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.174030Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_yoast_primary_term.ibd' OS error: 103
2025-06-10T12:22:17.174399Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.174745Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.175142Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_yoast_primary_term`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.175861Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_yoast_primary_term` because it could not be opened.
2025-06-10T12:22:17.176266Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.176565Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.176858Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.177241Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri01\wp_yoast_seo_links.ibd' OS error: 103
2025-06-10T12:22:17.177677Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.177943Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.178371Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri01/wp_yoast_seo_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.179051Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri01/wp_yoast_seo_links` because it could not be opened.
2025-06-10T12:22:17.179429Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.179748Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.180010Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.180383Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\7t_options.ibd' OS error: 103
2025-06-10T12:22:17.180764Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.181015Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.181479Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/7t_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.182245Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/7t_options` because it could not be opened.
2025-06-10T12:22:17.182665Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.182933Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.183204Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.183629Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_actionscheduler_actions.ibd' OS error: 103
2025-06-10T12:22:17.183984Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.184244Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.184711Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_actionscheduler_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.185301Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_actionscheduler_actions` because it could not be opened.
2025-06-10T12:22:17.185754Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.186021Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.186289Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.186693Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_actionscheduler_claims.ibd' OS error: 103
2025-06-10T12:22:17.187048Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.187308Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.187752Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_actionscheduler_claims`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.188357Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_actionscheduler_claims` because it could not be opened.
2025-06-10T12:22:17.188889Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.189155Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.189439Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.189842Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_actionscheduler_groups.ibd' OS error: 103
2025-06-10T12:22:17.190203Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.190695Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.191126Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_actionscheduler_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.191745Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_actionscheduler_groups` because it could not be opened.
2025-06-10T12:22:17.192152Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.192405Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.192831Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.193191Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_actionscheduler_logs.ibd' OS error: 103
2025-06-10T12:22:17.193571Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.193819Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.195122Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_actionscheduler_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.195994Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_actionscheduler_logs` because it could not be opened.
2025-06-10T12:22:17.197179Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.198107Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.198375Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.198805Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:17.199144Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.199417Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.199936Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.200576Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:17.201087Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.201352Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.201653Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.202035Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_comments.ibd' OS error: 103
2025-06-10T12:22:17.202363Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.202652Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.203071Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.203665Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_comments` because it could not be opened.
2025-06-10T12:22:17.204134Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.204402Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.204719Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.205102Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:17.205422Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.205733Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.206165Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.206759Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_fbv` because it could not be opened.
2025-06-10T12:22:17.207180Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.207443Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.207742Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.208120Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:17.208468Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.208763Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.209169Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.209775Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:17.210182Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.210444Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.210742Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.211120Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_links.ibd' OS error: 103
2025-06-10T12:22:17.211441Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.211734Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.212143Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.212728Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_links` because it could not be opened.
2025-06-10T12:22:17.213108Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.213358Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.213658Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.214042Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_newsletter.ibd' OS error: 103
2025-06-10T12:22:17.214353Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.214633Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.215087Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_newsletter`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.215703Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_newsletter` because it could not be opened.
2025-06-10T12:22:17.216113Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.216363Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.216671Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.217069Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_newsletter_emails.ibd' OS error: 103
2025-06-10T12:22:17.217396Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.217692Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.218132Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_newsletter_emails`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.218809Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_newsletter_emails` because it could not be opened.
2025-06-10T12:22:17.219594Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.219889Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.220164Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.220583Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_newsletter_sent.ibd' OS error: 103
2025-06-10T12:22:17.220951Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.221213Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.221673Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_newsletter_sent`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.222240Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_newsletter_sent` because it could not be opened.
2025-06-10T12:22:17.222753Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.223040Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.223311Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.223725Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_newsletter_stats.ibd' OS error: 103
2025-06-10T12:22:17.224111Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.224373Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.224842Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_newsletter_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.225506Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_newsletter_stats` because it could not be opened.
2025-06-10T12:22:17.226015Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.226297Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.226661Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.227127Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_newsletter_user_logs.ibd' OS error: 103
2025-06-10T12:22:17.227775Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.228028Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.228626Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_newsletter_user_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.229518Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_newsletter_user_logs` because it could not be opened.
2025-06-10T12:22:17.230039Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.230530Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.230805Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.231327Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_ngg_album.ibd' OS error: 103
2025-06-10T12:22:17.231700Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.231978Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.232460Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_ngg_album`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.233034Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_ngg_album` because it could not be opened.
2025-06-10T12:22:17.233550Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.233820Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.234090Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.234560Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_ngg_gallery.ibd' OS error: 103
2025-06-10T12:22:17.234898Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.235228Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.235636Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_ngg_gallery`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.236319Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_ngg_gallery` because it could not be opened.
2025-06-10T12:22:17.236757Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.237028Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.237421Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.237853Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_ngg_pictures.ibd' OS error: 103
2025-06-10T12:22:17.238238Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.238511Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.238954Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_ngg_pictures`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.239551Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_ngg_pictures` because it could not be opened.
2025-06-10T12:22:17.239986Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.240388Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.240690Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.241202Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_options.ibd' OS error: 103
2025-06-10T12:22:17.241638Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.241940Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.242379Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.242944Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_options` because it could not be opened.
2025-06-10T12:22:17.243381Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.243648Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.243920Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.244481Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_post_views.ibd' OS error: 103
2025-06-10T12:22:17.244835Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.245170Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.245776Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_post_views`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.246479Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_post_views` because it could not be opened.
2025-06-10T12:22:17.246911Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.247274Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.247552Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.247928Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:17.248342Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.248604Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.249013Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.249646Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_postmeta` because it could not be opened.
2025-06-10T12:22:17.250053Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.250414Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.250691Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.251135Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_posts.ibd' OS error: 103
2025-06-10T12:22:17.251471Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.251733Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.252212Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.252803Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_posts` because it could not be opened.
2025-06-10T12:22:17.253310Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.253579Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.253853Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.254306Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_revslider_css.ibd' OS error: 103
2025-06-10T12:22:17.254644Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.254900Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.255375Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_revslider_css`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.255948Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_revslider_css` because it could not be opened.
2025-06-10T12:22:17.256399Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.256661Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.256927Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.257372Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_revslider_css_bkp.ibd' OS error: 103
2025-06-10T12:22:17.257713Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.257973Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.258474Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_revslider_css_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.259119Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_revslider_css_bkp` because it could not be opened.
2025-06-10T12:22:17.259519Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.259782Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.260093Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.260482Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_revslider_layer_animations.ibd' OS error: 103
2025-06-10T12:22:17.260842Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.261153Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.261557Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_revslider_layer_animations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.262220Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_revslider_layer_animations` because it could not be opened.
2025-06-10T12:22:17.262607Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.262856Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.263288Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.263658Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_revslider_layer_animations_bkp.ibd' OS error: 103
2025-06-10T12:22:17.264011Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.264577Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.266300Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_revslider_layer_animations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.267438Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_revslider_layer_animations_bkp` because it could not be opened.
2025-06-10T12:22:17.268583Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.268923Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.269275Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.269661Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_revslider_navigations.ibd' OS error: 103
2025-06-10T12:22:17.270044Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.270335Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.270777Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_revslider_navigations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.271358Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_revslider_navigations` because it could not be opened.
2025-06-10T12:22:17.271834Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.272099Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.272370Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.272796Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_revslider_navigations_bkp.ibd' OS error: 103
2025-06-10T12:22:17.273164Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.273428Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.273891Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_revslider_navigations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.274500Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_revslider_navigations_bkp` because it could not be opened.
2025-06-10T12:22:17.275080Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.275422Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.275777Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.276286Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_revslider_sliders.ibd' OS error: 103
2025-06-10T12:22:17.276710Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.277001Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.277463Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_revslider_sliders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.278091Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_revslider_sliders` because it could not be opened.
2025-06-10T12:22:17.278515Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.278822Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.279216Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.279609Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_revslider_sliders_bkp.ibd' OS error: 103
2025-06-10T12:22:17.280120Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.280373Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.280891Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_revslider_sliders_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.281493Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_revslider_sliders_bkp` because it could not be opened.
2025-06-10T12:22:17.282010Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.282277Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.282546Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.282959Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_revslider_slides.ibd' OS error: 103
2025-06-10T12:22:17.283308Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.283570Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.284008Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_revslider_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.284623Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_revslider_slides` because it could not be opened.
2025-06-10T12:22:17.285087Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.285429Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.285849Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.286303Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_revslider_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:17.286691Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.287004Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.287395Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_revslider_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.288095Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_revslider_slides_bkp` because it could not be opened.
2025-06-10T12:22:17.288764Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.289152Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.289503Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.290071Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_revslider_static_slides.ibd' OS error: 103
2025-06-10T12:22:17.290657Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.290945Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.291597Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_revslider_static_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.292289Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_revslider_static_slides` because it could not be opened.
2025-06-10T12:22:17.292934Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.293198Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.293681Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.294156Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_revslider_static_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:17.294531Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.294968Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.295636Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_revslider_static_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.296305Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_revslider_static_slides_bkp` because it could not be opened.
2025-06-10T12:22:17.299637Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.300236Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.300624Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.301123Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_sbi_instagram_feeds_posts.ibd' OS error: 103
2025-06-10T12:22:17.301597Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.301876Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.302295Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_sbi_instagram_feeds_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.302961Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_sbi_instagram_feeds_posts` because it could not be opened.
2025-06-10T12:22:17.303479Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.303754Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.304027Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.304458Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_sbi_instagram_posts.ibd' OS error: 103
2025-06-10T12:22:17.304813Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.305072Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.305532Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_sbi_instagram_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.306118Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_sbi_instagram_posts` because it could not be opened.
2025-06-10T12:22:17.306561Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.306827Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.307242Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.307739Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:17.308109Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.308462Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.308855Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.309512Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:17.309907Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.310163Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.310541Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.310968Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:17.311387Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.311747Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.312161Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.312828Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:17.313235Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.313749Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.314034Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.314546Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:17.315014Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.315260Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.315775Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.316439Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_termmeta` because it could not be opened.
2025-06-10T12:22:17.317259Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.317583Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.317859Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.318230Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_terms.ibd' OS error: 103
2025-06-10T12:22:17.318636Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.318889Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.319314Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.319911Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_terms` because it could not be opened.
2025-06-10T12:22:17.320311Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.320848Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.321128Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.321610Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:17.322023Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.322367Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.323034Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.324254Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_usermeta` because it could not be opened.
2025-06-10T12:22:17.326232Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.326567Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.326930Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.327421Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_users.ibd' OS error: 103
2025-06-10T12:22:17.327771Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.328026Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.328517Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.329075Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_users` because it could not be opened.
2025-06-10T12:22:17.329593Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.329864Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.330136Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.330550Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_wc_admin_note_actions.ibd' OS error: 103
2025-06-10T12:22:17.330908Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.331174Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.331621Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_wc_admin_note_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.332274Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_wc_admin_note_actions` because it could not be opened.
2025-06-10T12:22:17.332746Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.333013Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.333352Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.333776Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_wc_admin_notes.ibd' OS error: 103
2025-06-10T12:22:17.334127Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.334451Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.334868Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_wc_admin_notes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.335498Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_wc_admin_notes` because it could not be opened.
2025-06-10T12:22:17.335936Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.336207Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.336530Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.336891Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_wc_category_lookup.ibd' OS error: 103
2025-06-10T12:22:17.337307Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.337621Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.338032Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_wc_category_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.338644Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_wc_category_lookup` because it could not be opened.
2025-06-10T12:22:17.339047Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.339341Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.339609Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.339993Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_wc_customer_lookup.ibd' OS error: 103
2025-06-10T12:22:17.340373Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.340654Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.341063Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_wc_customer_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.341673Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_wc_customer_lookup` because it could not be opened.
2025-06-10T12:22:17.342306Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.342588Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.342856Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.343314Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_wc_download_log.ibd' OS error: 103
2025-06-10T12:22:17.343664Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.343913Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.344401Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_wc_download_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.344957Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_wc_download_log` because it could not be opened.
2025-06-10T12:22:17.345460Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.345769Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.346028Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.346474Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_wc_order_coupon_lookup.ibd' OS error: 103
2025-06-10T12:22:17.346928Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.347206Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.347625Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_wc_order_coupon_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.348228Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_wc_order_coupon_lookup` because it could not be opened.
2025-06-10T12:22:17.348691Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.348960Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.349260Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.349644Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_wc_order_product_lookup.ibd' OS error: 103
2025-06-10T12:22:17.350000Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.350288Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.350696Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_wc_order_product_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.351352Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_wc_order_product_lookup` because it could not be opened.
2025-06-10T12:22:17.351779Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.352046Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.352335Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.352716Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_wc_order_stats.ibd' OS error: 103
2025-06-10T12:22:17.353052Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.353347Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.353758Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_wc_order_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.354399Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_wc_order_stats` because it could not be opened.
2025-06-10T12:22:17.354787Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.355053Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.355404Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.355770Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_wc_order_tax_lookup.ibd' OS error: 103
2025-06-10T12:22:17.356108Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.356438Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.356831Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_wc_order_tax_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.357454Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_wc_order_tax_lookup` because it could not be opened.
2025-06-10T12:22:17.357846Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.358098Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.358450Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.358811Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_wc_product_meta_lookup.ibd' OS error: 103
2025-06-10T12:22:17.359183Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.359483Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.359877Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_wc_product_meta_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.360537Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_wc_product_meta_lookup` because it could not be opened.
2025-06-10T12:22:17.360992Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.361284Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.361542Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.361923Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_wc_reserved_stock.ibd' OS error: 103
2025-06-10T12:22:17.362302Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.362585Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.363000Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_wc_reserved_stock`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.363605Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_wc_reserved_stock` because it could not be opened.
2025-06-10T12:22:17.364008Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.364301Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.364574Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.364991Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_wc_tax_rate_classes.ibd' OS error: 103
2025-06-10T12:22:17.365365Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.365627Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.366042Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_wc_tax_rate_classes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.366656Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_wc_tax_rate_classes` because it could not be opened.
2025-06-10T12:22:17.367068Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.367425Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.367697Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.368079Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_wc_webhooks.ibd' OS error: 103
2025-06-10T12:22:17.368452Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.368713Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.369141Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_wc_webhooks`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.369724Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_wc_webhooks` because it could not be opened.
2025-06-10T12:22:17.370573Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.370868Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.371154Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.371551Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_woocommerce_api_keys.ibd' OS error: 103
2025-06-10T12:22:17.371890Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.372223Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.372755Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_woocommerce_api_keys`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.373596Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_woocommerce_api_keys` because it could not be opened.
2025-06-10T12:22:17.374159Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.374769Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.375077Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.375575Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_woocommerce_attribute_taxonomies.ibd' OS error: 103
2025-06-10T12:22:17.376388Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.376639Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.377112Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_woocommerce_attribute_taxonomies`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.377840Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_woocommerce_attribute_taxonomies` because it could not be opened.
2025-06-10T12:22:17.378626Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.378954Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.379221Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.379814Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_woocommerce_downloadable_product_permissions.ibd' OS error: 103
2025-06-10T12:22:17.380251Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.380511Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.381000Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_woocommerce_downloadable_product_permissions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.381763Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_woocommerce_downloadable_product_permissions` because it could not be opened.
2025-06-10T12:22:17.382545Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.383241Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.383515Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.384516Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_woocommerce_log.ibd' OS error: 103
2025-06-10T12:22:17.384893Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.385159Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.385627Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_woocommerce_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.386207Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_woocommerce_log` because it could not be opened.
2025-06-10T12:22:17.386698Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.386961Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.387233Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.387679Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_woocommerce_order_itemmeta.ibd' OS error: 103
2025-06-10T12:22:17.388048Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.388358Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.388891Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_woocommerce_order_itemmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.389592Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_woocommerce_order_itemmeta` because it could not be opened.
2025-06-10T12:22:17.390241Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.390583Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.390846Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.391208Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_woocommerce_order_items.ibd' OS error: 103
2025-06-10T12:22:17.391663Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.391917Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.392456Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_woocommerce_order_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.393058Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_woocommerce_order_items` because it could not be opened.
2025-06-10T12:22:17.393560Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.393833Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.394110Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.394544Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_woocommerce_payment_tokenmeta.ibd' OS error: 103
2025-06-10T12:22:17.394918Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.395183Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.395641Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_woocommerce_payment_tokenmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.396540Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_woocommerce_payment_tokenmeta` because it could not be opened.
2025-06-10T12:22:17.397235Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.397671Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.397991Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.398437Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_woocommerce_payment_tokens.ibd' OS error: 103
2025-06-10T12:22:17.398841Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.399086Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.399605Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_woocommerce_payment_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.400178Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_woocommerce_payment_tokens` because it could not be opened.
2025-06-10T12:22:17.400660Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.400912Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.401168Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.401628Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_woocommerce_sessions.ibd' OS error: 103
2025-06-10T12:22:17.402067Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.402432Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.402937Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_woocommerce_sessions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.403649Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_woocommerce_sessions` because it could not be opened.
2025-06-10T12:22:17.404134Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.404468Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.404750Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.405142Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_woocommerce_shipping_zone_locations.ibd' OS error: 103
2025-06-10T12:22:17.405577Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.405847Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.406360Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_woocommerce_shipping_zone_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.407479Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_woocommerce_shipping_zone_locations` because it could not be opened.
2025-06-10T12:22:17.409691Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.410913Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.412097Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.413046Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_woocommerce_shipping_zone_methods.ibd' OS error: 103
2025-06-10T12:22:17.414889Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.415165Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.415692Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_woocommerce_shipping_zone_methods`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.416385Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_woocommerce_shipping_zone_methods` because it could not be opened.
2025-06-10T12:22:17.416952Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.417252Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.417567Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.417948Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_woocommerce_shipping_zones.ibd' OS error: 103
2025-06-10T12:22:17.418315Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.418613Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.419029Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_woocommerce_shipping_zones`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.419697Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_woocommerce_shipping_zones` because it could not be opened.
2025-06-10T12:22:17.420177Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.420514Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.421019Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.421481Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_woocommerce_tax_rate_locations.ibd' OS error: 103
2025-06-10T12:22:17.421881Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.422149Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.422618Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_woocommerce_tax_rate_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.423250Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_woocommerce_tax_rate_locations` because it could not be opened.
2025-06-10T12:22:17.423867Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.424138Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.424432Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.424837Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_woocommerce_tax_rates.ibd' OS error: 103
2025-06-10T12:22:17.425190Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.425508Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.425923Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_woocommerce_tax_rates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.426549Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_woocommerce_tax_rates` because it could not be opened.
2025-06-10T12:22:17.426993Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.427354Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.427664Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.428041Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:17.428411Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.428713Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.429154Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.429873Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:17.430310Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.430665Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.430927Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.431296Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:17.431747Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.432014Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.432518Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.433079Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:17.433696Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.434022Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.434300Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.434749Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:17.435161Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.435563Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.436049Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.436722Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:17.437124Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.437472Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.437795Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.438218Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:17.438650Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.438902Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.439301Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.440008Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:17.440468Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.440741Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.441003Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.441395Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_yith_wcwl.ibd' OS error: 103
2025-06-10T12:22:17.441814Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.442076Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.442503Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_yith_wcwl`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.443074Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_yith_wcwl` because it could not be opened.
2025-06-10T12:22:17.443634Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.443910Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.444186Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.444608Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_yith_wcwl_lists.ibd' OS error: 103
2025-06-10T12:22:17.444950Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.445213Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.445777Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_yith_wcwl_lists`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.446414Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_yith_wcwl_lists` because it could not be opened.
2025-06-10T12:22:17.446890Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.447156Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.447454Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.447835Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_yoast_indexable.ibd' OS error: 103
2025-06-10T12:22:17.448175Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.448529Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.448981Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_yoast_indexable`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.449726Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_yoast_indexable` because it could not be opened.
2025-06-10T12:22:17.450125Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.450420Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.450690Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.451068Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_yoast_indexable_hierarchy.ibd' OS error: 103
2025-06-10T12:22:17.451459Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.451719Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.452127Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_yoast_indexable_hierarchy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.452750Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_yoast_indexable_hierarchy` because it could not be opened.
2025-06-10T12:22:17.453159Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.453450Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.453716Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.454075Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_yoast_migrations.ibd' OS error: 103
2025-06-10T12:22:17.454465Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.454755Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.455256Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_yoast_migrations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.456972Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_yoast_migrations` because it could not be opened.
2025-06-10T12:22:17.457480Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.457954Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.458237Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.459134Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_yoast_primary_term.ibd' OS error: 103
2025-06-10T12:22:17.459641Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.459900Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.460523Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_yoast_primary_term`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.461553Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_yoast_primary_term` because it could not be opened.
2025-06-10T12:22:17.462717Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.463115Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.463402Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.463917Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri02\wp_yoast_seo_links.ibd' OS error: 103
2025-06-10T12:22:17.464273Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.464531Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.464941Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri02/wp_yoast_seo_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.465552Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri02/wp_yoast_seo_links` because it could not be opened.
2025-06-10T12:22:17.465975Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.466293Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.466561Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.467030Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\8r_options.ibd' OS error: 103
2025-06-10T12:22:17.467395Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.467661Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.468110Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/8r_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.468701Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/8r_options` because it could not be opened.
2025-06-10T12:22:17.469189Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.469562Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.469881Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.470324Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\fk_options.ibd' OS error: 103
2025-06-10T12:22:17.470667Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.470938Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.471415Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/fk_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.472222Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/fk_options` because it could not be opened.
2025-06-10T12:22:17.472706Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.472983Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.473277Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.473661Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\s2_options.ibd' OS error: 103
2025-06-10T12:22:17.473988Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.474278Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.474722Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/s2_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.475302Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/s2_options` because it could not be opened.
2025-06-10T12:22:17.475716Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.475981Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.476295Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.476700Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_actionscheduler_actions.ibd' OS error: 103
2025-06-10T12:22:17.477086Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.477689Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.478150Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_actionscheduler_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.478760Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_actionscheduler_actions` because it could not be opened.
2025-06-10T12:22:17.479350Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.479629Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.479899Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.480313Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_actionscheduler_claims.ibd' OS error: 103
2025-06-10T12:22:17.480680Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.480940Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.481377Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_actionscheduler_claims`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.481966Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_actionscheduler_claims` because it could not be opened.
2025-06-10T12:22:17.482427Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.482694Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.482963Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.483392Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_actionscheduler_groups.ibd' OS error: 103
2025-06-10T12:22:17.483749Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.484007Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.484471Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_actionscheduler_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.485093Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_actionscheduler_groups` because it could not be opened.
2025-06-10T12:22:17.485525Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.485789Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.486100Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.486530Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_actionscheduler_logs.ibd' OS error: 103
2025-06-10T12:22:17.486880Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.487159Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.487573Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_actionscheduler_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.488233Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_actionscheduler_logs` because it could not be opened.
2025-06-10T12:22:17.488744Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.489098Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.489639Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.490291Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:17.490670Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.491346Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.491852Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.492607Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:17.493052Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.493424Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.493807Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.494166Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_comments.ibd' OS error: 103
2025-06-10T12:22:17.494590Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.494933Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.495384Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.496026Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_comments` because it could not be opened.
2025-06-10T12:22:17.496597Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.496965Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.497245Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.497834Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:17.498207Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.498521Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.499029Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.499678Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_fbv` because it could not be opened.
2025-06-10T12:22:17.500111Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.500460Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.500734Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.501122Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:17.501556Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.501819Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.502233Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.502916Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:17.503501Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.503783Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.504055Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.504643Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_links.ibd' OS error: 103
2025-06-10T12:22:17.505005Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.505325Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.506001Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.506621Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_links` because it could not be opened.
2025-06-10T12:22:17.507031Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.507393Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.507682Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.508041Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_newsletter.ibd' OS error: 103
2025-06-10T12:22:17.508432Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.508687Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.509225Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_newsletter`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.509883Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_newsletter` because it could not be opened.
2025-06-10T12:22:17.510356Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.510629Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.510901Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.511372Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_newsletter_emails.ibd' OS error: 103
2025-06-10T12:22:17.511711Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.511959Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.512480Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_newsletter_emails`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.513212Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_newsletter_emails` because it could not be opened.
2025-06-10T12:22:17.513871Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.514127Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.514505Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.514872Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_newsletter_sent.ibd' OS error: 103
2025-06-10T12:22:17.515200Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.515551Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.516099Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_newsletter_sent`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.516824Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_newsletter_sent` because it could not be opened.
2025-06-10T12:22:17.517213Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.517554Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.517812Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.518175Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_newsletter_stats.ibd' OS error: 103
2025-06-10T12:22:17.518599Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.518847Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.519310Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_newsletter_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.519876Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_newsletter_stats` because it could not be opened.
2025-06-10T12:22:17.520365Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.520673Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.520925Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.521423Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_newsletter_user_logs.ibd' OS error: 103
2025-06-10T12:22:17.521754Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.521997Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.522506Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_newsletter_user_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.523050Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_newsletter_user_logs` because it could not be opened.
2025-06-10T12:22:17.523546Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.523797Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.524059Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.524621Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_ngg_album.ibd' OS error: 103
2025-06-10T12:22:17.524940Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.525328Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.525740Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_ngg_album`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.526371Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_ngg_album` because it could not be opened.
2025-06-10T12:22:17.526765Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.527017Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.527348Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.527713Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_ngg_gallery.ibd' OS error: 103
2025-06-10T12:22:17.528022Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.528363Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.528787Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_ngg_gallery`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.529512Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_ngg_gallery` because it could not be opened.
2025-06-10T12:22:17.530131Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.530549Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.530867Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.531537Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_ngg_pictures.ibd' OS error: 103
2025-06-10T12:22:17.531886Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.532144Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.532642Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_ngg_pictures`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.533234Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_ngg_pictures` because it could not be opened.
2025-06-10T12:22:17.533684Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.533939Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.534242Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.534631Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_options.ibd' OS error: 103
2025-06-10T12:22:17.535080Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.535767Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.536257Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.537462Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_options` because it could not be opened.
2025-06-10T12:22:17.538181Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.538758Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.539017Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.539504Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_post_views.ibd' OS error: 103
2025-06-10T12:22:17.539861Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.540539Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.541011Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_post_views`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.541667Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_post_views` because it could not be opened.
2025-06-10T12:22:17.542335Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.542742Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.543011Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.543742Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:17.544072Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.544336Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.544812Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.545377Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_postmeta` because it could not be opened.
2025-06-10T12:22:17.545964Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.546250Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.546544Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.546938Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_posts.ibd' OS error: 103
2025-06-10T12:22:17.547265Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.547554Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.548005Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.548631Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_posts` because it could not be opened.
2025-06-10T12:22:17.549063Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.549333Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.549679Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.550095Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_revslider_css.ibd' OS error: 103
2025-06-10T12:22:17.550444Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.550780Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.551236Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_revslider_css`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.552069Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_revslider_css` because it could not be opened.
2025-06-10T12:22:17.552569Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.552859Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.553135Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.553532Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_revslider_css_bkp.ibd' OS error: 103
2025-06-10T12:22:17.553891Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.554155Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.554606Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_revslider_css_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.555253Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_revslider_css_bkp` because it could not be opened.
2025-06-10T12:22:17.555728Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.556004Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.556279Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.556708Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_revslider_layer_animations.ibd' OS error: 103
2025-06-10T12:22:17.557079Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.557355Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.557830Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_revslider_layer_animations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.558445Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_revslider_layer_animations` because it could not be opened.
2025-06-10T12:22:17.558935Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.559304Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.559854Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.560314Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_revslider_layer_animations_bkp.ibd' OS error: 103
2025-06-10T12:22:17.560810Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.561133Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.561586Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_revslider_layer_animations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.562321Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_revslider_layer_animations_bkp` because it could not be opened.
2025-06-10T12:22:17.562932Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.563194Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.563455Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.563887Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_revslider_navigations.ibd' OS error: 103
2025-06-10T12:22:17.564221Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.564466Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.565101Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_revslider_navigations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.565989Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_revslider_navigations` because it could not be opened.
2025-06-10T12:22:17.566424Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.566772Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.567034Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.567398Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_revslider_navigations_bkp.ibd' OS error: 103
2025-06-10T12:22:17.567882Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.568130Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.568694Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_revslider_navigations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.569427Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_revslider_navigations_bkp` because it could not be opened.
2025-06-10T12:22:17.570220Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.570618Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.570873Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.571691Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_revslider_sliders.ibd' OS error: 103
2025-06-10T12:22:17.572119Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.572382Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.573027Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_revslider_sliders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.573945Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_revslider_sliders` because it could not be opened.
2025-06-10T12:22:17.574451Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.574763Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.575095Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.575476Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_revslider_sliders_bkp.ibd' OS error: 103
2025-06-10T12:22:17.576356Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.576927Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.577412Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_revslider_sliders_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.578070Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_revslider_sliders_bkp` because it could not be opened.
2025-06-10T12:22:17.578516Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.578784Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.579053Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.579533Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_revslider_slides.ibd' OS error: 103
2025-06-10T12:22:17.579879Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.580149Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.580617Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_revslider_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.581206Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_revslider_slides` because it could not be opened.
2025-06-10T12:22:17.581690Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.581958Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.582311Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.582755Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_revslider_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:17.583308Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.583646Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.584057Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_revslider_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.584837Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_revslider_slides_bkp` because it could not be opened.
2025-06-10T12:22:17.585409Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.585673Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.585934Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.586348Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_revslider_static_slides.ibd' OS error: 103
2025-06-10T12:22:17.586798Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.587050Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.587628Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_revslider_static_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.588212Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_revslider_static_slides` because it could not be opened.
2025-06-10T12:22:17.588810Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.589069Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.589418Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.589810Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_revslider_static_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:17.590185Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.590511Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.590902Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_revslider_static_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.591709Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_revslider_static_slides_bkp` because it could not be opened.
2025-06-10T12:22:17.592283Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.592579Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.592868Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.593284Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_sbi_instagram_feeds_posts.ibd' OS error: 103
2025-06-10T12:22:17.593731Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.594089Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.594556Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_sbi_instagram_feeds_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.595160Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_sbi_instagram_feeds_posts` because it could not be opened.
2025-06-10T12:22:17.595689Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.595955Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.596279Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.596667Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_sbi_instagram_posts.ibd' OS error: 103
2025-06-10T12:22:17.597019Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.597340Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.597751Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_sbi_instagram_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.598385Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_sbi_instagram_posts` because it could not be opened.
2025-06-10T12:22:17.598790Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.599052Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.599380Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.599760Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:17.600285Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.600546Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.601117Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.601824Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:17.602324Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.602587Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.602928Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.603384Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:17.603941Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.604374Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.605051Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.606970Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:17.607931Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.608314Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.608799Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.609592Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:17.609980Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.610244Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.610741Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.611289Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_termmeta` because it could not be opened.
2025-06-10T12:22:17.611775Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.612034Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.612298Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.612740Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_terms.ibd' OS error: 103
2025-06-10T12:22:17.613058Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.613314Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.613791Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.614339Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_terms` because it could not be opened.
2025-06-10T12:22:17.614965Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.615294Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.615653Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.616021Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:17.616497Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.616775Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.617177Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.617816Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_usermeta` because it could not be opened.
2025-06-10T12:22:17.618260Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.618583Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.618981Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.619415Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_users.ibd' OS error: 103
2025-06-10T12:22:17.619762Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.620028Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.620494Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.621055Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_users` because it could not be opened.
2025-06-10T12:22:17.621500Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.621772Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.622039Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.622470Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_wc_admin_note_actions.ibd' OS error: 103
2025-06-10T12:22:17.622924Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.623186Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.623666Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_wc_admin_note_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.624256Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_wc_admin_note_actions` because it could not be opened.
2025-06-10T12:22:17.624748Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.625013Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.625371Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.625805Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_wc_admin_notes.ibd' OS error: 103
2025-06-10T12:22:17.626189Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.626586Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.627053Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_wc_admin_notes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.627700Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_wc_admin_notes` because it could not be opened.
2025-06-10T12:22:17.628095Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.628433Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.628773Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.629167Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_wc_category_lookup.ibd' OS error: 103
2025-06-10T12:22:17.629578Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.629841Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.630235Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_wc_category_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.630848Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_wc_category_lookup` because it could not be opened.
2025-06-10T12:22:17.631243Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.631545Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.631856Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.632246Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_wc_customer_lookup.ibd' OS error: 103
2025-06-10T12:22:17.632676Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.632927Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.633320Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_wc_customer_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.633938Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_wc_customer_lookup` because it could not be opened.
2025-06-10T12:22:17.634328Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.634678Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.635204Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.635672Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_wc_download_log.ibd' OS error: 103
2025-06-10T12:22:17.636025Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.636304Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.636777Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_wc_download_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.637384Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_wc_download_log` because it could not be opened.
2025-06-10T12:22:17.637840Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.638112Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.638398Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.638837Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_wc_order_coupon_lookup.ibd' OS error: 103
2025-06-10T12:22:17.639191Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.639508Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.639901Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_wc_order_coupon_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.640532Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_wc_order_coupon_lookup` because it could not be opened.
2025-06-10T12:22:17.640951Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.641203Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.641541Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.641920Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_wc_order_product_lookup.ibd' OS error: 103
2025-06-10T12:22:17.642263Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.642577Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.642965Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_wc_order_product_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.643621Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_wc_order_product_lookup` because it could not be opened.
2025-06-10T12:22:17.644007Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.644258Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.644610Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.645001Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_wc_order_stats.ibd' OS error: 103
2025-06-10T12:22:17.645326Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.645670Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.646064Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_wc_order_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.646740Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_wc_order_stats` because it could not be opened.
2025-06-10T12:22:17.647415Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.648585Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.649270Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.649675Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_wc_order_tax_lookup.ibd' OS error: 103
2025-06-10T12:22:17.650526Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.650777Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.651419Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_wc_order_tax_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.652073Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_wc_order_tax_lookup` because it could not be opened.
2025-06-10T12:22:17.652582Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.652962Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.653230Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.653789Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_wc_product_meta_lookup.ibd' OS error: 103
2025-06-10T12:22:17.654129Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.654499Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.654995Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_wc_product_meta_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.655597Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_wc_product_meta_lookup` because it could not be opened.
2025-06-10T12:22:17.656067Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.656386Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.656711Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.657311Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_wc_reserved_stock.ibd' OS error: 103
2025-06-10T12:22:17.657713Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.658037Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.658455Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_wc_reserved_stock`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.659104Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_wc_reserved_stock` because it could not be opened.
2025-06-10T12:22:17.659554Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.659816Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.660154Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.660604Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_wc_tax_rate_classes.ibd' OS error: 103
2025-06-10T12:22:17.661027Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.661313Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.661732Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_wc_tax_rate_classes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.662379Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_wc_tax_rate_classes` because it could not be opened.
2025-06-10T12:22:17.662853Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.663180Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.663591Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.664026Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_wc_webhooks.ibd' OS error: 103
2025-06-10T12:22:17.664384Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.664688Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.665178Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_wc_webhooks`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.665728Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_wc_webhooks` because it could not be opened.
2025-06-10T12:22:17.666245Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.666557Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.666817Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.667326Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_woocommerce_api_keys.ibd' OS error: 103
2025-06-10T12:22:17.667758Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.668082Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.668504Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_woocommerce_api_keys`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.669148Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_woocommerce_api_keys` because it could not be opened.
2025-06-10T12:22:17.669678Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.670047Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.670326Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.670864Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_woocommerce_attribute_taxonomies.ibd' OS error: 103
2025-06-10T12:22:17.671304Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.671629Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.672131Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_woocommerce_attribute_taxonomies`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.672752Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_woocommerce_attribute_taxonomies` because it could not be opened.
2025-06-10T12:22:17.673279Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.673530Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.673787Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.674241Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_woocommerce_downloadable_product_permissions.ibd' OS error: 103
2025-06-10T12:22:17.674622Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.674867Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.675354Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_woocommerce_downloadable_product_permissions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.676038Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_woocommerce_downloadable_product_permissions` because it could not be opened.
2025-06-10T12:22:17.676485Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.676736Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.677043Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.677467Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_woocommerce_log.ibd' OS error: 103
2025-06-10T12:22:17.677827Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.678193Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.678579Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_woocommerce_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.679212Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_woocommerce_log` because it could not be opened.
2025-06-10T12:22:17.679581Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.679830Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.680293Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.681130Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_woocommerce_order_itemmeta.ibd' OS error: 103
2025-06-10T12:22:17.681939Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.682297Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.682710Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_woocommerce_order_itemmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.683445Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_woocommerce_order_itemmeta` because it could not be opened.
2025-06-10T12:22:17.684521Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.684788Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.685248Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.685922Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_woocommerce_order_items.ibd' OS error: 103
2025-06-10T12:22:17.686263Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.686593Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.688250Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_woocommerce_order_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.689077Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_woocommerce_order_items` because it could not be opened.
2025-06-10T12:22:17.689578Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.690137Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.690564Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.691044Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_woocommerce_payment_tokenmeta.ibd' OS error: 103
2025-06-10T12:22:17.691403Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.691684Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.692170Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_woocommerce_payment_tokenmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.692880Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_woocommerce_payment_tokenmeta` because it could not be opened.
2025-06-10T12:22:17.693375Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.693650Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.694046Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.694420Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_woocommerce_payment_tokens.ibd' OS error: 103
2025-06-10T12:22:17.694941Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.695425Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.696112Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_woocommerce_payment_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.697114Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_woocommerce_payment_tokens` because it could not be opened.
2025-06-10T12:22:17.697765Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.698133Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.698398Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.698772Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_woocommerce_sessions.ibd' OS error: 103
2025-06-10T12:22:17.699200Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.699450Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.699930Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_woocommerce_sessions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.700582Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_woocommerce_sessions` because it could not be opened.
2025-06-10T12:22:17.701121Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.701396Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.701653Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.702072Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_woocommerce_shipping_zone_locations.ibd' OS error: 103
2025-06-10T12:22:17.702446Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.702693Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.703144Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_woocommerce_shipping_zone_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.703741Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_woocommerce_shipping_zone_locations` because it could not be opened.
2025-06-10T12:22:17.704198Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.704459Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.704730Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.705145Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_woocommerce_shipping_zone_methods.ibd' OS error: 103
2025-06-10T12:22:17.705524Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.705806Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.706212Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_woocommerce_shipping_zone_methods`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.706853Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_woocommerce_shipping_zone_methods` because it could not be opened.
2025-06-10T12:22:17.707273Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.707534Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.707831Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.708213Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_woocommerce_shipping_zones.ibd' OS error: 103
2025-06-10T12:22:17.708556Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.708895Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.709336Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_woocommerce_shipping_zones`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.710029Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_woocommerce_shipping_zones` because it could not be opened.
2025-06-10T12:22:17.710433Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.710678Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.710993Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.711354Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_woocommerce_tax_rate_locations.ibd' OS error: 103
2025-06-10T12:22:17.711709Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.712020Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.712404Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_woocommerce_tax_rate_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.713050Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_woocommerce_tax_rate_locations` because it could not be opened.
2025-06-10T12:22:17.713495Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.713771Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.714110Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.714482Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_woocommerce_tax_rates.ibd' OS error: 103
2025-06-10T12:22:17.714882Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.715130Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.715662Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_woocommerce_tax_rates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.716289Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_woocommerce_tax_rates` because it could not be opened.
2025-06-10T12:22:17.716774Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.717085Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.717358Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.717726Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:17.718150Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.718397Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.718837Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.719403Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:17.719880Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.720145Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.721487Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.722100Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:17.722811Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.723161Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.723651Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.724285Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:17.724727Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.724979Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.725237Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.725664Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:17.725976Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.726226Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.726683Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.727223Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:17.727766Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.728173Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.728501Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.728867Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:17.729242Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.729715Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.730224Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.730931Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:17.731401Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.731667Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.731935Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.732358Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_yith_wcwl.ibd' OS error: 103
2025-06-10T12:22:17.732731Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.733019Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.733514Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_yith_wcwl`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.734052Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_yith_wcwl` because it could not be opened.
2025-06-10T12:22:17.734491Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.734743Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.735127Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.735640Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_yith_wcwl_lists.ibd' OS error: 103
2025-06-10T12:22:17.735966Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.736214Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.736695Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_yith_wcwl_lists`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.737301Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_yith_wcwl_lists` because it could not be opened.
2025-06-10T12:22:17.737709Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.737956Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.738207Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.738640Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_yoast_indexable.ibd' OS error: 103
2025-06-10T12:22:17.738955Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.739278Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.739732Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_yoast_indexable`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.740398Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_yoast_indexable` because it could not be opened.
2025-06-10T12:22:17.740806Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.741116Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.741492Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.741865Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_yoast_indexable_hierarchy.ibd' OS error: 103
2025-06-10T12:22:17.742291Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.742622Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.743007Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_yoast_indexable_hierarchy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.743726Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_yoast_indexable_hierarchy` because it could not be opened.
2025-06-10T12:22:17.744118Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.744518Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.744790Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.745177Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_yoast_migrations.ibd' OS error: 103
2025-06-10T12:22:17.745578Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.745841Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.746370Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_yoast_migrations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.746951Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_yoast_migrations` because it could not be opened.
2025-06-10T12:22:17.747434Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.747702Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.748045Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.748548Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_yoast_primary_term.ibd' OS error: 103
2025-06-10T12:22:17.748885Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.749181Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.749805Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_yoast_primary_term`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.750518Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_yoast_primary_term` because it could not be opened.
2025-06-10T12:22:17.750928Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.751283Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.751566Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.751926Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_biofri03\wp_yoast_seo_links.ibd' OS error: 103
2025-06-10T12:22:17.752366Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.752613Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.753162Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_biofri03/wp_yoast_seo_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.754163Z 0 [Warning] InnoDB: Ignoring tablespace `client_biofri03/wp_yoast_seo_links` because it could not be opened.
2025-06-10T12:22:17.755453Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.756008Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.756360Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.756768Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_actionscheduler_actions.ibd' OS error: 103
2025-06-10T12:22:17.757192Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.757470Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.757912Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_actionscheduler_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.758515Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_actionscheduler_actions` because it could not be opened.
2025-06-10T12:22:17.759012Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.759282Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.759556Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.759971Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_actionscheduler_claims.ibd' OS error: 103
2025-06-10T12:22:17.760345Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.760613Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.761077Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_actionscheduler_claims`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.761683Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_actionscheduler_claims` because it could not be opened.
2025-06-10T12:22:17.762206Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.762752Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.763107Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.763550Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_actionscheduler_groups.ibd' OS error: 103
2025-06-10T12:22:17.763994Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.764245Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.764641Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_actionscheduler_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.765263Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_actionscheduler_groups` because it could not be opened.
2025-06-10T12:22:17.765692Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.766043Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.766322Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.766673Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_actionscheduler_logs.ibd' OS error: 103
2025-06-10T12:22:17.767084Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.767326Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.767739Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_actionscheduler_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.768324Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_actionscheduler_logs` because it could not be opened.
2025-06-10T12:22:17.768737Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.769152Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.769477Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.769880Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:17.770216Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.770473Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.770983Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.771554Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:17.772042Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.772307Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.772576Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.773011Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_comments.ibd' OS error: 103
2025-06-10T12:22:17.773341Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.773601Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.774064Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.774621Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_comments` because it could not be opened.
2025-06-10T12:22:17.775082Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.775353Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.775621Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.776099Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_links.ibd' OS error: 103
2025-06-10T12:22:17.776409Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.776653Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.777163Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.777768Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_links` because it could not be opened.
2025-06-10T12:22:17.778142Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.778395Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.778652Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.779160Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_options.ibd' OS error: 103
2025-06-10T12:22:17.779761Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.780043Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.780454Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.781215Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_options` because it could not be opened.
2025-06-10T12:22:17.781884Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.782281Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.782596Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.783056Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:17.783388Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.783858Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.785329Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.786239Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_postmeta` because it could not be opened.
2025-06-10T12:22:17.787015Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.787299Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.787570Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.787987Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_posts.ibd' OS error: 103
2025-06-10T12:22:17.788308Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.788564Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.789042Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.789602Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_posts` because it could not be opened.
2025-06-10T12:22:17.790068Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.790333Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.790857Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.791273Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_revslider_css.ibd' OS error: 103
2025-06-10T12:22:17.791612Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.792013Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.792423Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_revslider_css`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.793135Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_revslider_css` because it could not be opened.
2025-06-10T12:22:17.793655Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.794018Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.794372Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.794802Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_revslider_css_bkp.ibd' OS error: 103
2025-06-10T12:22:17.795156Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.795405Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.795926Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_revslider_css_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.796593Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_revslider_css_bkp` because it could not be opened.
2025-06-10T12:22:17.797166Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.797644Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.797995Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.798364Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_revslider_layer_animations.ibd' OS error: 103
2025-06-10T12:22:17.798760Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.799043Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.799433Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_revslider_layer_animations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.800308Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_revslider_layer_animations` because it could not be opened.
2025-06-10T12:22:17.800794Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.801097Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.801360Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.801867Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_revslider_layer_animations_bkp.ibd' OS error: 103
2025-06-10T12:22:17.802234Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.802480Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.802950Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_revslider_layer_animations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.803573Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_revslider_layer_animations_bkp` because it could not be opened.
2025-06-10T12:22:17.804222Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.804496Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.804895Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.805372Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_revslider_navigations.ibd' OS error: 103
2025-06-10T12:22:17.805809Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.806103Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.806496Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_revslider_navigations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.807256Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_revslider_navigations` because it could not be opened.
2025-06-10T12:22:17.807664Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.807989Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.808242Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.808590Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_revslider_navigations_bkp.ibd' OS error: 103
2025-06-10T12:22:17.809130Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.809393Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.809849Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_revslider_navigations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.810538Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_revslider_navigations_bkp` because it could not be opened.
2025-06-10T12:22:17.810996Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.811264Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.811535Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.811981Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_revslider_sliders.ibd' OS error: 103
2025-06-10T12:22:17.812341Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.812606Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.813104Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_revslider_sliders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.813726Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_revslider_sliders` because it could not be opened.
2025-06-10T12:22:17.814163Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.814426Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.814748Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.815130Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_revslider_sliders_bkp.ibd' OS error: 103
2025-06-10T12:22:17.815535Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.815974Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.816609Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_revslider_sliders_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.817589Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_revslider_sliders_bkp` because it could not be opened.
2025-06-10T12:22:17.818628Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.818922Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.819211Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.819618Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_revslider_slides.ibd' OS error: 103
2025-06-10T12:22:17.819990Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.820255Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.820694Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_revslider_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.821286Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_revslider_slides` because it could not be opened.
2025-06-10T12:22:17.821738Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.822025Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.822301Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.822705Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_revslider_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:17.823068Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.823529Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.824043Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_revslider_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.824670Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_revslider_slides_bkp` because it could not be opened.
2025-06-10T12:22:17.825150Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.825469Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.825831Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.826261Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_revslider_static_slides.ibd' OS error: 103
2025-06-10T12:22:17.826660Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.826903Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.827287Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_revslider_static_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.827948Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_revslider_static_slides` because it could not be opened.
2025-06-10T12:22:17.828361Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.828711Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.828960Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.829354Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_revslider_static_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:17.830056Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.830342Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.830843Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_revslider_static_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.831562Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_revslider_static_slides_bkp` because it could not be opened.
2025-06-10T12:22:17.832082Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.832353Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.832664Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.833031Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:17.833368Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.833751Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.834159Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.834831Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:17.835534Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.835812Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.836223Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.836688Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:17.837018Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.837276Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.837728Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.838269Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:17.838750Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.839039Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.839295Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.839747Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:17.840069Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.840328Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.840774Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.841571Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_termmeta` because it could not be opened.
2025-06-10T12:22:17.842036Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.842326Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.842762Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.843155Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_terms.ibd' OS error: 103
2025-06-10T12:22:17.843558Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.843863Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.844262Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.844957Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_terms` because it could not be opened.
2025-06-10T12:22:17.845513Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.845834Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.846256Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.846723Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:17.847041Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.847288Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.847798Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.848444Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_usermeta` because it could not be opened.
2025-06-10T12:22:17.849239Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.849896Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.850569Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.851127Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_users.ibd' OS error: 103
2025-06-10T12:22:17.851491Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.851753Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.852192Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.852759Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_users` because it could not be opened.
2025-06-10T12:22:17.853206Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.853475Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.853747Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.854157Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_wc_admin_note_actions.ibd' OS error: 103
2025-06-10T12:22:17.854522Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.854810Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.855235Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_wc_admin_note_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.855886Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_wc_admin_note_actions` because it could not be opened.
2025-06-10T12:22:17.856376Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.856646Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.856958Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.857370Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_wc_admin_notes.ibd' OS error: 103
2025-06-10T12:22:17.857735Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.858046Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.858493Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_wc_admin_notes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.859100Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_wc_admin_notes` because it could not be opened.
2025-06-10T12:22:17.859518Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.859807Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.860083Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.860468Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_wc_category_lookup.ibd' OS error: 103
2025-06-10T12:22:17.860871Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.861156Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.861561Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_wc_category_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.862395Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_wc_category_lookup` because it could not be opened.
2025-06-10T12:22:17.862903Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.863191Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.863468Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.863882Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_wc_customer_lookup.ibd' OS error: 103
2025-06-10T12:22:17.864231Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.864491Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.864942Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_wc_customer_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.865524Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_wc_customer_lookup` because it could not be opened.
2025-06-10T12:22:17.865953Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.866221Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.866491Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.866900Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_wc_download_log.ibd' OS error: 103
2025-06-10T12:22:17.867248Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.867509Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.867955Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_wc_download_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.868544Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_wc_download_log` because it could not be opened.
2025-06-10T12:22:17.868989Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.869241Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.869499Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.869928Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_wc_order_coupon_lookup.ibd' OS error: 103
2025-06-10T12:22:17.870272Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.870518Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.870964Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_wc_order_coupon_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.871534Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_wc_order_coupon_lookup` because it could not be opened.
2025-06-10T12:22:17.871983Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.872237Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.872495Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.872942Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_wc_order_product_lookup.ibd' OS error: 103
2025-06-10T12:22:17.873302Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.873561Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.874025Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_wc_order_product_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.874652Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_wc_order_product_lookup` because it could not be opened.
2025-06-10T12:22:17.875123Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.875377Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.875635Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.876068Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_wc_order_stats.ibd' OS error: 103
2025-06-10T12:22:17.876405Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.876691Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.877156Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_wc_order_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.877721Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_wc_order_stats` because it could not be opened.
2025-06-10T12:22:17.878169Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.878421Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.878679Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.879138Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_wc_order_tax_lookup.ibd' OS error: 103
2025-06-10T12:22:17.879475Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.879810Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.880221Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_wc_order_tax_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.881023Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_wc_order_tax_lookup` because it could not be opened.
2025-06-10T12:22:17.881969Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.882369Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.882898Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.883517Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_wc_product_meta_lookup.ibd' OS error: 103
2025-06-10T12:22:17.884098Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.884581Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.885196Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_wc_product_meta_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.886112Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_wc_product_meta_lookup` because it could not be opened.
2025-06-10T12:22:17.886834Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.887228Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.887715Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.888260Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_wc_reserved_stock.ibd' OS error: 103
2025-06-10T12:22:17.888863Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.889252Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.889950Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_wc_reserved_stock`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.890747Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_wc_reserved_stock` because it could not be opened.
2025-06-10T12:22:17.891173Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.891426Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.891838Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.892215Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_wc_tax_rate_classes.ibd' OS error: 103
2025-06-10T12:22:17.892592Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.892863Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.893249Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_wc_tax_rate_classes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.893983Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_wc_tax_rate_classes` because it could not be opened.
2025-06-10T12:22:17.894529Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.894816Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.895076Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.895443Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_wc_webhooks.ibd' OS error: 103
2025-06-10T12:22:17.895856Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.896240Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.896734Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_wc_webhooks`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.897356Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_wc_webhooks` because it could not be opened.
2025-06-10T12:22:17.897896Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.898154Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.898550Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.898996Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_woocommerce_api_keys.ibd' OS error: 103
2025-06-10T12:22:17.899342Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.899707Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.900115Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_woocommerce_api_keys`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.900751Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_woocommerce_api_keys` because it could not be opened.
2025-06-10T12:22:17.901193Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.901462Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.901931Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.902321Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_woocommerce_attribute_taxonomies.ibd' OS error: 103
2025-06-10T12:22:17.902730Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.902996Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.903410Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_woocommerce_attribute_taxonomies`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.904087Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_woocommerce_attribute_taxonomies` because it could not be opened.
2025-06-10T12:22:17.904656Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.904920Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.905182Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.905634Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_woocommerce_downloadable_product_permissions.ibd' OS error: 103
2025-06-10T12:22:17.906059Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.906310Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.906867Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_woocommerce_downloadable_product_permissions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.907607Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_woocommerce_downloadable_product_permissions` because it could not be opened.
2025-06-10T12:22:17.908110Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.908382Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.908687Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.909116Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_woocommerce_log.ibd' OS error: 103
2025-06-10T12:22:17.909493Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.909829Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.910221Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_woocommerce_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.911001Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_woocommerce_log` because it could not be opened.
2025-06-10T12:22:17.911576Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.912109Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.912370Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.913995Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_woocommerce_order_itemmeta.ibd' OS error: 103
2025-06-10T12:22:17.914499Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.914774Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.915259Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_woocommerce_order_itemmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.915861Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_woocommerce_order_itemmeta` because it could not be opened.
2025-06-10T12:22:17.916387Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.916643Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.916900Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.917358Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_woocommerce_order_items.ibd' OS error: 103
2025-06-10T12:22:17.917704Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.917955Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.918453Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_woocommerce_order_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.919201Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_woocommerce_order_items` because it could not be opened.
2025-06-10T12:22:17.919698Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.919978Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.920487Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.920891Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_woocommerce_payment_tokenmeta.ibd' OS error: 103
2025-06-10T12:22:17.921377Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.921646Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.922266Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_woocommerce_payment_tokenmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.923035Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_woocommerce_payment_tokenmeta` because it could not be opened.
2025-06-10T12:22:17.923536Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.923791Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.924046Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.924590Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_woocommerce_payment_tokens.ibd' OS error: 103
2025-06-10T12:22:17.924935Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.925302Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.925686Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_woocommerce_payment_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.926442Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_woocommerce_payment_tokens` because it could not be opened.
2025-06-10T12:22:17.926914Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.927286Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.927543Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.927907Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_woocommerce_sessions.ibd' OS error: 103
2025-06-10T12:22:17.928374Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.928629Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.929006Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_woocommerce_sessions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.929785Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_woocommerce_sessions` because it could not be opened.
2025-06-10T12:22:17.930267Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.930512Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.930763Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.931234Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_woocommerce_shipping_zone_locations.ibd' OS error: 103
2025-06-10T12:22:17.931606Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.931845Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.932333Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_woocommerce_shipping_zone_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.932994Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_woocommerce_shipping_zone_locations` because it could not be opened.
2025-06-10T12:22:17.933499Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.933782Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.934191Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.934551Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_woocommerce_shipping_zone_methods.ibd' OS error: 103
2025-06-10T12:22:17.934913Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.935254Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.935817Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_woocommerce_shipping_zone_methods`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.936493Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_woocommerce_shipping_zone_methods` because it could not be opened.
2025-06-10T12:22:17.936971Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.937275Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.937551Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.937934Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_woocommerce_shipping_zones.ibd' OS error: 103
2025-06-10T12:22:17.938330Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.938590Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.939004Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_woocommerce_shipping_zones`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.939698Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_woocommerce_shipping_zones` because it could not be opened.
2025-06-10T12:22:17.940221Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.940496Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.940811Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.941324Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_woocommerce_tax_rate_locations.ibd' OS error: 103
2025-06-10T12:22:17.941701Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.941970Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.942475Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_woocommerce_tax_rate_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.943161Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_woocommerce_tax_rate_locations` because it could not be opened.
2025-06-10T12:22:17.943618Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.943880Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.944355Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.945052Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_woocommerce_tax_rates.ibd' OS error: 103
2025-06-10T12:22:17.945777Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.946218Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.947055Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_woocommerce_tax_rates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.948044Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_woocommerce_tax_rates` because it could not be opened.
2025-06-10T12:22:17.948729Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.949154Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.949558Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.949948Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:17.950353Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.950623Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.951223Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.951860Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:17.952474Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.952734Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.953051Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.953461Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:17.953790Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.954145Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.954593Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.955364Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:17.955816Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.956122Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.956390Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.956766Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:17.957125Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.957384Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.957812Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.958449Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:17.958891Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.959206Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.959467Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.959833Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup1\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:17.960233Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.960492Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.960904Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup1/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.961515Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup1/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:17.962148Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.962410Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.962671Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.963087Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_actionscheduler_actions.ibd' OS error: 103
2025-06-10T12:22:17.963481Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.963729Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.964183Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_actionscheduler_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.964888Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_actionscheduler_actions` because it could not be opened.
2025-06-10T12:22:17.965384Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.965644Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.965905Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.966354Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_actionscheduler_claims.ibd' OS error: 103
2025-06-10T12:22:17.966748Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.967111Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.967582Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_actionscheduler_claims`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.968240Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_actionscheduler_claims` because it could not be opened.
2025-06-10T12:22:17.968651Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.968961Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.969278Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.969641Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_actionscheduler_groups.ibd' OS error: 103
2025-06-10T12:22:17.970096Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.970401Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.970790Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_actionscheduler_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.971456Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_actionscheduler_groups` because it could not be opened.
2025-06-10T12:22:17.971863Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.972187Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.972446Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.972805Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_actionscheduler_logs.ibd' OS error: 103
2025-06-10T12:22:17.973277Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.973526Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.973973Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_actionscheduler_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.974587Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_actionscheduler_logs` because it could not be opened.
2025-06-10T12:22:17.975073Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.975326Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.975582Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.976149Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:17.976477Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.976724Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.977348Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.977937Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:17.978342Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.978588Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.978839Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.979393Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_comments.ibd' OS error: 103
2025-06-10T12:22:17.979700Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.980078Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.980471Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.981108Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_comments` because it could not be opened.
2025-06-10T12:22:17.981464Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.981708Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.982119Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.982475Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_links.ibd' OS error: 103
2025-06-10T12:22:17.982774Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.983165Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.983578Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.984224Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_links` because it could not be opened.
2025-06-10T12:22:17.984562Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.984808Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.985201Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.985562Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_options.ibd' OS error: 103
2025-06-10T12:22:17.985932Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.986268Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.986706Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.987324Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_options` because it could not be opened.
2025-06-10T12:22:17.987712Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.988037Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.988308Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.988696Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:17.989124Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.989624Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.990193Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.990757Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_postmeta` because it could not be opened.
2025-06-10T12:22:17.991223Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.991474Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.991733Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.992516Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_posts.ibd' OS error: 103
2025-06-10T12:22:17.993127Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.993390Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.994000Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.994926Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_posts` because it could not be opened.
2025-06-10T12:22:17.995378Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.995649Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.995996Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.996540Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_revslider_css.ibd' OS error: 103
2025-06-10T12:22:17.996907Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:17.997169Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:17.997581Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_revslider_css`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:17.998203Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_revslider_css` because it could not be opened.
2025-06-10T12:22:17.998661Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:17.998981Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:17.999255Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:17.999643Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_revslider_css_bkp.ibd' OS error: 103
2025-06-10T12:22:18.000059Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.000322Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.000748Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_revslider_css_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.001430Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_revslider_css_bkp` because it could not be opened.
2025-06-10T12:22:18.001994Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.002291Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.002642Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.003152Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_revslider_layer_animations.ibd' OS error: 103
2025-06-10T12:22:18.003531Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.003809Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.004223Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_revslider_layer_animations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.004905Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_revslider_layer_animations` because it could not be opened.
2025-06-10T12:22:18.005397Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.005667Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.005953Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.006334Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_revslider_layer_animations_bkp.ibd' OS error: 103
2025-06-10T12:22:18.006712Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.007048Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.007456Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_revslider_layer_animations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.008128Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_revslider_layer_animations_bkp` because it could not be opened.
2025-06-10T12:22:18.008564Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.008897Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.009169Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.009546Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_revslider_navigations.ibd' OS error: 103
2025-06-10T12:22:18.009970Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.010232Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.010640Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_revslider_navigations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.011283Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_revslider_navigations` because it could not be opened.
2025-06-10T12:22:18.011686Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.012012Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.012282Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.012660Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_revslider_navigations_bkp.ibd' OS error: 103
2025-06-10T12:22:18.013091Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.013353Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.013836Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_revslider_navigations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.014462Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_revslider_navigations_bkp` because it could not be opened.
2025-06-10T12:22:18.014939Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.015253Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.015531Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.015925Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_revslider_sliders.ibd' OS error: 103
2025-06-10T12:22:18.016271Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.016536Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.016998Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_revslider_sliders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.017582Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_revslider_sliders` because it could not be opened.
2025-06-10T12:22:18.018026Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.018290Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.018557Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.019002Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_revslider_sliders_bkp.ibd' OS error: 103
2025-06-10T12:22:18.019360Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.019618Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.020080Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_revslider_sliders_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.020679Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_revslider_sliders_bkp` because it could not be opened.
2025-06-10T12:22:18.021182Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.021446Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.021763Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.022152Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_revslider_slides.ibd' OS error: 103
2025-06-10T12:22:18.022497Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.022806Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.023221Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_revslider_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.023882Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_revslider_slides` because it could not be opened.
2025-06-10T12:22:18.024564Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.024837Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.025603Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.026001Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_revslider_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:18.026729Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.026994Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.027406Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_revslider_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.028106Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_revslider_slides_bkp` because it could not be opened.
2025-06-10T12:22:18.028571Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.028835Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.029105Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.029550Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_revslider_static_slides.ibd' OS error: 103
2025-06-10T12:22:18.029914Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.030239Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.030727Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_revslider_static_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.031459Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_revslider_static_slides` because it could not be opened.
2025-06-10T12:22:18.032037Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.032311Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.032641Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.033036Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_revslider_static_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:18.033513Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.033802Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.034310Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_revslider_static_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.034946Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_revslider_static_slides_bkp` because it could not be opened.
2025-06-10T12:22:18.035424Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.035704Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.035975Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.036486Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:18.036874Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.037138Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.037633Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.038222Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:18.038692Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.039146Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.039455Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.039905Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:18.040414Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.040690Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.041100Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.041710Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:18.042103Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.042366Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.042676Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.043058Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:18.043411Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.043692Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.044104Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.044719Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_termmeta` because it could not be opened.
2025-06-10T12:22:18.045098Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.045379Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.045670Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.046075Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_terms.ibd' OS error: 103
2025-06-10T12:22:18.046456Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.046754Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.047171Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.047756Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_terms` because it could not be opened.
2025-06-10T12:22:18.048200Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.048531Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.048813Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.049206Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:18.049584Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.049850Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.050269Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.050884Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_usermeta` because it could not be opened.
2025-06-10T12:22:18.051295Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.051594Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.051948Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.052387Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_users.ibd' OS error: 103
2025-06-10T12:22:18.052887Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.053250Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.053734Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.054296Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_users` because it could not be opened.
2025-06-10T12:22:18.054802Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.055071Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.055356Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.056641Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_wc_admin_note_actions.ibd' OS error: 103
2025-06-10T12:22:18.058431Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.058755Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.059181Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_wc_admin_note_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.059814Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_wc_admin_note_actions` because it could not be opened.
2025-06-10T12:22:18.060256Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.060651Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.061022Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.061572Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_wc_admin_notes.ibd' OS error: 103
2025-06-10T12:22:18.061944Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.062200Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.062715Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_wc_admin_notes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.063271Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_wc_admin_notes` because it could not be opened.
2025-06-10T12:22:18.063795Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.064056Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.064315Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.064839Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_wc_category_lookup.ibd' OS error: 103
2025-06-10T12:22:18.065175Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.065588Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.066052Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_wc_category_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.066703Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_wc_category_lookup` because it could not be opened.
2025-06-10T12:22:18.067114Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.067591Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.067894Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.068271Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_wc_customer_lookup.ibd' OS error: 103
2025-06-10T12:22:18.068701Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.068952Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.069390Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_wc_customer_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.069962Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_wc_customer_lookup` because it could not be opened.
2025-06-10T12:22:18.070412Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.070720Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.070980Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.071389Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_wc_download_log.ibd' OS error: 103
2025-06-10T12:22:18.071731Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.071978Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.072412Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_wc_download_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.073010Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_wc_download_log` because it could not be opened.
2025-06-10T12:22:18.073482Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.073968Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.074257Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.074696Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_wc_order_coupon_lookup.ibd' OS error: 103
2025-06-10T12:22:18.075035Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.075294Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.075748Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_wc_order_coupon_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.076376Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_wc_order_coupon_lookup` because it could not be opened.
2025-06-10T12:22:18.076933Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.077193Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.077604Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.077983Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_wc_order_product_lookup.ibd' OS error: 103
2025-06-10T12:22:18.078418Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.078683Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.079068Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_wc_order_product_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.079906Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_wc_order_product_lookup` because it could not be opened.
2025-06-10T12:22:18.080349Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.080618Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.080873Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.081234Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_wc_order_stats.ibd' OS error: 103
2025-06-10T12:22:18.081642Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.081893Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.082470Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_wc_order_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.083022Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_wc_order_stats` because it could not be opened.
2025-06-10T12:22:18.083528Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.083794Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.084073Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.084566Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_wc_order_tax_lookup.ibd' OS error: 103
2025-06-10T12:22:18.084926Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.085275Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.085706Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_wc_order_tax_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.086365Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_wc_order_tax_lookup` because it could not be opened.
2025-06-10T12:22:18.086881Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.087128Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.087503Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.087959Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_wc_product_meta_lookup.ibd' OS error: 103
2025-06-10T12:22:18.088684Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.088943Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.089454Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_wc_product_meta_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.090551Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_wc_product_meta_lookup` because it could not be opened.
2025-06-10T12:22:18.091156Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.091565Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.091842Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.092217Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_wc_reserved_stock.ibd' OS error: 103
2025-06-10T12:22:18.092741Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.092988Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.093820Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_wc_reserved_stock`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.094506Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_wc_reserved_stock` because it could not be opened.
2025-06-10T12:22:18.094976Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.095234Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.095561Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.095948Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_wc_tax_rate_classes.ibd' OS error: 103
2025-06-10T12:22:18.096312Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.096609Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.097021Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_wc_tax_rate_classes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.097846Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_wc_tax_rate_classes` because it could not be opened.
2025-06-10T12:22:18.098548Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.099128Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.099527Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.099893Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_wc_webhooks.ibd' OS error: 103
2025-06-10T12:22:18.100216Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.100601Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.101107Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_wc_webhooks`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.101754Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_wc_webhooks` because it could not be opened.
2025-06-10T12:22:18.102167Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.102518Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.102778Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.103139Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_woocommerce_api_keys.ibd' OS error: 103
2025-06-10T12:22:18.103623Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.103988Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.104558Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_woocommerce_api_keys`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.105388Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_woocommerce_api_keys` because it could not be opened.
2025-06-10T12:22:18.105839Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.106098Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.106442Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.106880Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_woocommerce_attribute_taxonomies.ibd' OS error: 103
2025-06-10T12:22:18.107250Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.107579Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.108045Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_woocommerce_attribute_taxonomies`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.108785Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_woocommerce_attribute_taxonomies` because it could not be opened.
2025-06-10T12:22:18.109246Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.109550Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.109811Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.110182Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_woocommerce_downloadable_product_permissions.ibd' OS error: 103
2025-06-10T12:22:18.110642Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.110897Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.111342Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_woocommerce_downloadable_product_permissions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.111985Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_woocommerce_downloadable_product_permissions` because it could not be opened.
2025-06-10T12:22:18.112556Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.112827Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.113087Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.113533Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_woocommerce_log.ibd' OS error: 103
2025-06-10T12:22:18.113916Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.114475Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.114908Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_woocommerce_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.115626Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_woocommerce_log` because it could not be opened.
2025-06-10T12:22:18.116020Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.116323Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.116591Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.117018Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_woocommerce_order_itemmeta.ibd' OS error: 103
2025-06-10T12:22:18.117572Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.117880Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.118454Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_woocommerce_order_itemmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.119122Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_woocommerce_order_itemmeta` because it could not be opened.
2025-06-10T12:22:18.119631Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.119902Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.120176Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.120743Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_woocommerce_order_items.ibd' OS error: 103
2025-06-10T12:22:18.121243Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.121521Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.122034Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_woocommerce_order_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.123228Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_woocommerce_order_items` because it could not be opened.
2025-06-10T12:22:18.123708Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.124001Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.124295Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.124682Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_woocommerce_payment_tokenmeta.ibd' OS error: 103
2025-06-10T12:22:18.125060Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.125356Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.125771Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_woocommerce_payment_tokenmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.126431Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_woocommerce_payment_tokenmeta` because it could not be opened.
2025-06-10T12:22:18.126905Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.127211Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.127491Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.127884Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_woocommerce_payment_tokens.ibd' OS error: 103
2025-06-10T12:22:18.128362Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.128639Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.129059Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_woocommerce_payment_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.129748Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_woocommerce_payment_tokens` because it could not be opened.
2025-06-10T12:22:18.130293Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.130585Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.130896Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.131301Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_woocommerce_sessions.ibd' OS error: 103
2025-06-10T12:22:18.131658Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.131919Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.132358Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_woocommerce_sessions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.132951Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_woocommerce_sessions` because it could not be opened.
2025-06-10T12:22:18.133409Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.133675Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.133949Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.134363Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_woocommerce_shipping_zone_locations.ibd' OS error: 103
2025-06-10T12:22:18.134788Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.135046Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.135488Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_woocommerce_shipping_zone_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.136095Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_woocommerce_shipping_zone_locations` because it could not be opened.
2025-06-10T12:22:18.136568Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.136819Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.137181Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.137664Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_woocommerce_shipping_zone_methods.ibd' OS error: 103
2025-06-10T12:22:18.138039Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.138427Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.138942Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_woocommerce_shipping_zone_methods`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.139679Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_woocommerce_shipping_zone_methods` because it could not be opened.
2025-06-10T12:22:18.140144Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.140695Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.141058Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.141553Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_woocommerce_shipping_zones.ibd' OS error: 103
2025-06-10T12:22:18.141932Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.142236Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.142641Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_woocommerce_shipping_zones`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.143336Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_woocommerce_shipping_zones` because it could not be opened.
2025-06-10T12:22:18.143750Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.144017Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.144358Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.144733Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_woocommerce_tax_rate_locations.ibd' OS error: 103
2025-06-10T12:22:18.145142Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.145418Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.145816Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_woocommerce_tax_rate_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.146512Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_woocommerce_tax_rate_locations` because it could not be opened.
2025-06-10T12:22:18.146949Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.147283Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.147548Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.148028Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_woocommerce_tax_rates.ibd' OS error: 103
2025-06-10T12:22:18.148422Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.148686Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.149186Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_woocommerce_tax_rates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.149808Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_woocommerce_tax_rates` because it could not be opened.
2025-06-10T12:22:18.150321Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.150578Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.150842Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.151265Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:18.151621Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.151907Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.152403Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.153880Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:18.154452Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.154743Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.155208Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.156177Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:18.156618Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.156932Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.157487Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.158096Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:18.158572Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.158823Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.159161Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.159687Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:18.160092Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.160601Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.161065Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.161763Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:18.162357Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.162737Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.163072Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.163471Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup2\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:18.163840Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.164150Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.164542Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup2/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.165183Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup2/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:18.165628Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.165887Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.166207Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.166574Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_actionscheduler_actions.ibd' OS error: 103
2025-06-10T12:22:18.166916Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.167226Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.167617Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_actionscheduler_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.168282Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_actionscheduler_actions` because it could not be opened.
2025-06-10T12:22:18.168697Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.169029Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.169300Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.169879Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_actionscheduler_claims.ibd' OS error: 103
2025-06-10T12:22:18.170315Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.170623Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.171074Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_actionscheduler_claims`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.171682Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_actionscheduler_claims` because it could not be opened.
2025-06-10T12:22:18.172335Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.172730Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.173077Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.173550Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_actionscheduler_groups.ibd' OS error: 103
2025-06-10T12:22:18.173906Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.174313Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.174850Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_actionscheduler_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.175631Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_actionscheduler_groups` because it could not be opened.
2025-06-10T12:22:18.176243Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.176607Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.177099Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.177658Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_actionscheduler_logs.ibd' OS error: 103
2025-06-10T12:22:18.178389Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.178674Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.179138Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_actionscheduler_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.179705Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_actionscheduler_logs` because it could not be opened.
2025-06-10T12:22:18.180197Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.180449Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.180747Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.181209Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:18.181551Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.181819Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.182320Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.183022Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:18.183518Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.183771Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.184372Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.185229Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_comments.ibd' OS error: 103
2025-06-10T12:22:18.185935Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.186451Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.187014Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.187630Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_comments` because it could not be opened.
2025-06-10T12:22:18.188158Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.188462Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.188738Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.189194Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_links.ibd' OS error: 103
2025-06-10T12:22:18.189558Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.189876Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.190297Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.190941Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_links` because it could not be opened.
2025-06-10T12:22:18.191396Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.191660Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.192013Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.192404Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_options.ibd' OS error: 103
2025-06-10T12:22:18.192738Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.193094Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.193516Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.194349Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_options` because it could not be opened.
2025-06-10T12:22:18.195112Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.195495Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.195966Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.196670Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:18.197248Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.197618Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.198292Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.199017Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_postmeta` because it could not be opened.
2025-06-10T12:22:18.199487Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.199793Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.200094Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.200478Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_posts.ibd' OS error: 103
2025-06-10T12:22:18.200828Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.201101Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.201532Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.202127Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_posts` because it could not be opened.
2025-06-10T12:22:18.202526Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.202819Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.203093Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.203479Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_revslider_css.ibd' OS error: 103
2025-06-10T12:22:18.203850Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.204111Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.204517Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_revslider_css`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.205241Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_revslider_css` because it could not be opened.
2025-06-10T12:22:18.205707Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.206089Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.206351Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.206716Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_revslider_css_bkp.ibd' OS error: 103
2025-06-10T12:22:18.207144Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.207412Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.207870Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_revslider_css_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.208452Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_revslider_css_bkp` because it could not be opened.
2025-06-10T12:22:18.208901Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.209240Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.209519Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.209949Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_revslider_layer_animations.ibd' OS error: 103
2025-06-10T12:22:18.210324Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.210586Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.211033Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_revslider_layer_animations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.211676Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_revslider_layer_animations` because it could not be opened.
2025-06-10T12:22:18.212152Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.212433Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.212710Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.213134Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_revslider_layer_animations_bkp.ibd' OS error: 103
2025-06-10T12:22:18.213514Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.213818Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.214231Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_revslider_layer_animations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.214876Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_revslider_layer_animations_bkp` because it could not be opened.
2025-06-10T12:22:18.215334Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.215600Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.216255Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.216639Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_revslider_navigations.ibd' OS error: 103
2025-06-10T12:22:18.217873Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.218150Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.218675Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_revslider_navigations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.219413Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_revslider_navigations` because it could not be opened.
2025-06-10T12:22:18.219885Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.220162Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.220461Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.220886Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_revslider_navigations_bkp.ibd' OS error: 103
2025-06-10T12:22:18.221242Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.221556Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.221951Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_revslider_navigations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.222620Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_revslider_navigations_bkp` because it could not be opened.
2025-06-10T12:22:18.223082Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.223338Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.223663Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.224147Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_revslider_sliders.ibd' OS error: 103
2025-06-10T12:22:18.224672Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.224975Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.225440Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_revslider_sliders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.226118Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_revslider_sliders` because it could not be opened.
2025-06-10T12:22:18.226634Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.226909Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.227179Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.227591Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_revslider_sliders_bkp.ibd' OS error: 103
2025-06-10T12:22:18.227946Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.228206Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.228644Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_revslider_sliders_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.229234Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_revslider_sliders_bkp` because it could not be opened.
2025-06-10T12:22:18.229675Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.229937Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.230206Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.230610Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_revslider_slides.ibd' OS error: 103
2025-06-10T12:22:18.230953Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.231213Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.231647Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_revslider_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.232229Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_revslider_slides` because it could not be opened.
2025-06-10T12:22:18.232721Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.233016Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.233271Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.233766Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_revslider_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:18.234114Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.234430Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.234832Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_revslider_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.235454Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_revslider_slides_bkp` because it could not be opened.
2025-06-10T12:22:18.235872Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.236251Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.236570Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.236933Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_revslider_static_slides.ibd' OS error: 103
2025-06-10T12:22:18.237278Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.237591Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.237984Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_revslider_static_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.238614Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_revslider_static_slides` because it could not be opened.
2025-06-10T12:22:18.239099Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.239450Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.239748Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.240117Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_revslider_static_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:18.240591Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.240854Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.241334Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_revslider_static_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.241974Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_revslider_static_slides_bkp` because it could not be opened.
2025-06-10T12:22:18.242515Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.242856Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.243124Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.243547Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:18.243889Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.244142Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.244678Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.245317Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:18.245869Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.246241Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.246652Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.247091Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:18.247606Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.247960Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.248646Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.249215Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:18.249750Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.250019Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.250296Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.250793Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:18.251140Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.251495Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.251955Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.252766Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_termmeta` because it could not be opened.
2025-06-10T12:22:18.253201Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.253527Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.253786Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.254140Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_terms.ibd' OS error: 103
2025-06-10T12:22:18.254541Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.254785Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.255178Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.255783Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_terms` because it could not be opened.
2025-06-10T12:22:18.256145Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.256466Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.256717Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.257070Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:18.257497Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.257938Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.258671Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.259692Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_usermeta` because it could not be opened.
2025-06-10T12:22:18.260436Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.260713Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.260988Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.261536Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_users.ibd' OS error: 103
2025-06-10T12:22:18.261869Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.262143Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.262661Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.263178Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_users` because it could not be opened.
2025-06-10T12:22:18.263820Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.264198Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.264637Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.264996Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_wc_admin_note_actions.ibd' OS error: 103
2025-06-10T12:22:18.265464Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.265941Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.266440Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_wc_admin_note_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.266987Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_wc_admin_note_actions` because it could not be opened.
2025-06-10T12:22:18.267470Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.267735Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.268003Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.268435Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_wc_admin_notes.ibd' OS error: 103
2025-06-10T12:22:18.268772Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.269033Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.269507Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_wc_admin_notes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.270083Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_wc_admin_notes` because it could not be opened.
2025-06-10T12:22:18.270590Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.270917Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.271282Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.271726Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_wc_category_lookup.ibd' OS error: 103
2025-06-10T12:22:18.272848Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.273151Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.273645Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_wc_category_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.274539Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_wc_category_lookup` because it could not be opened.
2025-06-10T12:22:18.275052Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.275342Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.275620Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.276005Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_wc_customer_lookup.ibd' OS error: 103
2025-06-10T12:22:18.276393Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.276660Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.277077Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_wc_customer_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.277706Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_wc_customer_lookup` because it could not be opened.
2025-06-10T12:22:18.278164Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.278476Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.278994Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.279444Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_wc_download_log.ibd' OS error: 103
2025-06-10T12:22:18.279817Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.280092Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.280654Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_wc_download_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.281314Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_wc_download_log` because it could not be opened.
2025-06-10T12:22:18.281835Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.282112Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.282511Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.282892Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_wc_order_coupon_lookup.ibd' OS error: 103
2025-06-10T12:22:18.283328Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.283584Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.283982Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_wc_order_coupon_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.284625Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_wc_order_coupon_lookup` because it could not be opened.
2025-06-10T12:22:18.285048Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.285438Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.285700Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.286067Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_wc_order_product_lookup.ibd' OS error: 103
2025-06-10T12:22:18.286520Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.286771Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.287224Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_wc_order_product_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.287879Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_wc_order_product_lookup` because it could not be opened.
2025-06-10T12:22:18.288411Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.288667Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.288920Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.289382Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_wc_order_stats.ibd' OS error: 103
2025-06-10T12:22:18.289715Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.289964Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.290448Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_wc_order_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.291455Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_wc_order_stats` because it could not be opened.
2025-06-10T12:22:18.291982Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.292318Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.292580Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.292947Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_wc_order_tax_lookup.ibd' OS error: 103
2025-06-10T12:22:18.293428Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.293727Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.294492Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_wc_order_tax_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.295045Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_wc_order_tax_lookup` because it could not be opened.
2025-06-10T12:22:18.295714Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.296039Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.296357Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.297142Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_wc_product_meta_lookup.ibd' OS error: 103
2025-06-10T12:22:18.298866Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.299178Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.299782Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_wc_product_meta_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.300430Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_wc_product_meta_lookup` because it could not be opened.
2025-06-10T12:22:18.300875Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.301139Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.301448Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.301824Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_wc_reserved_stock.ibd' OS error: 103
2025-06-10T12:22:18.302171Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.302507Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.302921Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_wc_reserved_stock`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.303771Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_wc_reserved_stock` because it could not be opened.
2025-06-10T12:22:18.304242Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.304559Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.304827Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.305206Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_wc_tax_rate_classes.ibd' OS error: 103
2025-06-10T12:22:18.305649Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.305926Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.306400Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_wc_tax_rate_classes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.306991Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_wc_tax_rate_classes` because it could not be opened.
2025-06-10T12:22:18.307530Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.307818Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.308086Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.308529Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_wc_webhooks.ibd' OS error: 103
2025-06-10T12:22:18.308864Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.309125Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.309597Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_wc_webhooks`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.310239Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_wc_webhooks` because it could not be opened.
2025-06-10T12:22:18.310697Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.310967Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.311241Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.311658Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_woocommerce_api_keys.ibd' OS error: 103
2025-06-10T12:22:18.312018Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.312306Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.312746Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_woocommerce_api_keys`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.313366Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_woocommerce_api_keys` because it could not be opened.
2025-06-10T12:22:18.313802Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.314068Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.314460Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.314868Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_woocommerce_attribute_taxonomies.ibd' OS error: 103
2025-06-10T12:22:18.315250Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.315551Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.315956Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_woocommerce_attribute_taxonomies`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.316622Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_woocommerce_attribute_taxonomies` because it could not be opened.
2025-06-10T12:22:18.317064Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.317357Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.317627Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.318005Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_woocommerce_downloadable_product_permissions.ibd' OS error: 103
2025-06-10T12:22:18.318456Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.318738Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.319150Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_woocommerce_downloadable_product_permissions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.319829Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_woocommerce_downloadable_product_permissions` because it could not be opened.
2025-06-10T12:22:18.320314Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.320596Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.320902Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.321295Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_woocommerce_log.ibd' OS error: 103
2025-06-10T12:22:18.321656Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.321903Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.322362Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_woocommerce_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.322953Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_woocommerce_log` because it could not be opened.
2025-06-10T12:22:18.323408Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.323711Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.323981Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.324421Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_woocommerce_order_itemmeta.ibd' OS error: 103
2025-06-10T12:22:18.324773Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.325026Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.325592Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_woocommerce_order_itemmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.326497Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_woocommerce_order_itemmeta` because it could not be opened.
2025-06-10T12:22:18.326980Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.327288Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.327568Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.327946Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_woocommerce_order_items.ibd' OS error: 103
2025-06-10T12:22:18.328652Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.328955Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.329602Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_woocommerce_order_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.330711Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_woocommerce_order_items` because it could not be opened.
2025-06-10T12:22:18.331336Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.331648Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.331923Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.332323Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_woocommerce_payment_tokenmeta.ibd' OS error: 103
2025-06-10T12:22:18.332820Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.333116Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.333550Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_woocommerce_payment_tokenmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.334197Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_woocommerce_payment_tokenmeta` because it could not be opened.
2025-06-10T12:22:18.334657Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.334916Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.335260Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.335635Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_woocommerce_payment_tokens.ibd' OS error: 103
2025-06-10T12:22:18.335996Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.336340Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.336739Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_woocommerce_payment_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.337414Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_woocommerce_payment_tokens` because it could not be opened.
2025-06-10T12:22:18.337971Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.338312Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.338718Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.339240Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_woocommerce_sessions.ibd' OS error: 103
2025-06-10T12:22:18.339648Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.339895Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.340368Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_woocommerce_sessions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.340909Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_woocommerce_sessions` because it could not be opened.
2025-06-10T12:22:18.341394Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.341641Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.341893Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.342386Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_woocommerce_shipping_zone_locations.ibd' OS error: 103
2025-06-10T12:22:18.342750Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.342994Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.343546Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_woocommerce_shipping_zone_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.344173Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_woocommerce_shipping_zone_locations` because it could not be opened.
2025-06-10T12:22:18.344612Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.344869Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.345174Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.345546Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_woocommerce_shipping_zone_methods.ibd' OS error: 103
2025-06-10T12:22:18.346130Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.346402Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.346795Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_woocommerce_shipping_zone_methods`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.347452Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_woocommerce_shipping_zone_methods` because it could not be opened.
2025-06-10T12:22:18.347868Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.348167Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.348472Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.348856Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_woocommerce_shipping_zones.ibd' OS error: 103
2025-06-10T12:22:18.349240Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.349555Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.350026Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_woocommerce_shipping_zones`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.350655Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_woocommerce_shipping_zones` because it could not be opened.
2025-06-10T12:22:18.351169Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.351534Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.351790Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.352403Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_woocommerce_tax_rate_locations.ibd' OS error: 103
2025-06-10T12:22:18.352787Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.353067Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.353521Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_woocommerce_tax_rate_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.354227Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_woocommerce_tax_rate_locations` because it could not be opened.
2025-06-10T12:22:18.354655Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.354911Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.355306Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.355670Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_woocommerce_tax_rates.ibd' OS error: 103
2025-06-10T12:22:18.356013Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.356361Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.356757Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_woocommerce_tax_rates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.357473Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_woocommerce_tax_rates` because it could not be opened.
2025-06-10T12:22:18.358631Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.358929Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.359278Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.359648Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:18.359989Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.360664Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.361163Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.361823Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:18.362305Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.362945Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.363262Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.363678Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:18.364087Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.364362Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.364779Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.365413Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:18.365920Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.366192Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.366464Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.367067Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:18.367414Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.367682Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.368179Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.368759Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:18.369286Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.369573Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.369926Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.370450Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_careerup3\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:18.370805Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.371152Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.371588Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_careerup3/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.372357Z 0 [Warning] InnoDB: Ignoring tablespace `client_careerup3/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:18.373109Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.373404Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.373675Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.374195Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem0\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:18.374535Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.374889Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.375318Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem0/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.375912Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem0/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:18.376318Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.376576Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.376889Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.377307Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem0\wp_comments.ibd' OS error: 103
2025-06-10T12:22:18.377620Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.377962Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.378471Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem0/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.379124Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem0/wp_comments` because it could not be opened.
2025-06-10T12:22:18.379504Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.379761Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.380115Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.380480Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem0\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:18.380846Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.381129Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.381521Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem0/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.382173Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem0/wp_fbv` because it could not be opened.
2025-06-10T12:22:18.382522Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.382774Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.383126Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.383494Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem0\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:18.383952Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.384202Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.384594Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem0/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.385364Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem0/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:18.385842Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.386123Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.386397Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.386789Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem0\wp_links.ibd' OS error: 103
2025-06-10T12:22:18.387132Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.387400Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.387868Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem0/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.388445Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem0/wp_links` because it could not be opened.
2025-06-10T12:22:18.388881Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.389159Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.389504Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.389964Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem0\wp_options.ibd' OS error: 103
2025-06-10T12:22:18.390285Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.390538Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.391261Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem0/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.392120Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem0/wp_options` because it could not be opened.
2025-06-10T12:22:18.392845Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.393190Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.393469Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.394068Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem0\wp_post_views.ibd' OS error: 103
2025-06-10T12:22:18.394432Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.394727Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.395137Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem0/wp_post_views`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.395740Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem0/wp_post_views` because it could not be opened.
2025-06-10T12:22:18.396155Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.396422Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.396723Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.397268Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem0\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:18.397649Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.397953Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.398367Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem0/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.398986Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem0/wp_postmeta` because it could not be opened.
2025-06-10T12:22:18.399446Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.399754Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.400029Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.400413Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem0\wp_posts.ibd' OS error: 103
2025-06-10T12:22:18.400811Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.401073Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.401490Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem0/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.402099Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem0/wp_posts` because it could not be opened.
2025-06-10T12:22:18.402497Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.402789Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.403177Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.403667Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem0\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:18.404126Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.404428Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.404894Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem0/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.405456Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem0/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:18.405956Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.406211Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.406469Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.406939Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem0\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:18.407275Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.407526Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.407979Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem0/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.408609Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem0/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:18.409062Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.409322Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.409619Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.410007Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem0\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:18.410323Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.410609Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.411034Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem0/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.411616Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem0/wp_termmeta` because it could not be opened.
2025-06-10T12:22:18.412029Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.412281Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.412539Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.412985Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem0\wp_terms.ibd' OS error: 103
2025-06-10T12:22:18.413305Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.413590Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.414020Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem0/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.414610Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem0/wp_terms` because it could not be opened.
2025-06-10T12:22:18.414998Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.415262Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.415533Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.415974Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem0\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:18.416353Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.416671Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.417075Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem0/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.417706Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem0/wp_usermeta` because it could not be opened.
2025-06-10T12:22:18.418103Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.418360Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.418697Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.419235Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem0\wp_users.ibd' OS error: 103
2025-06-10T12:22:18.419649Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.419933Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.420376Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem0/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.420984Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem0/wp_users` because it could not be opened.
2025-06-10T12:22:18.421424Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.421747Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.422018Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.422395Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem0\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:18.422848Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.423110Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.423513Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem0/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.424140Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem0/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:18.424598Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.424893Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.425161Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.425553Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem0\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:18.425902Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.426160Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.426602Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem0/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.427182Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem0/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:18.427586Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.427854Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.428123Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.428738Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem0\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:18.429066Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.429312Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.429838Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem0/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.430374Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem0/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:18.430792Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.431042Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.431299Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.431723Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem0\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:18.432064Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.432312Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.432762Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem0/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.433321Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem0/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:18.434105Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.434392Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.434748Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.435126Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:18.435453Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.435785Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.436216Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.436895Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:18.437331Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.437679Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.437998Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.438371Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1\wp_comments.ibd' OS error: 103
2025-06-10T12:22:18.438783Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.439038Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.439528Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.440566Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1/wp_comments` because it could not be opened.
2025-06-10T12:22:18.441510Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.441832Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.442319Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.443129Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1\wp_gg_attributes.ibd' OS error: 103
2025-06-10T12:22:18.443484Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.443796Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.444211Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1/wp_gg_attributes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.444833Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1/wp_gg_attributes` because it could not be opened.
2025-06-10T12:22:18.445271Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.445535Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.445830Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.446217Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1\wp_gg_cdn.ibd' OS error: 103
2025-06-10T12:22:18.446538Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.446830Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.447246Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1/wp_gg_cdn`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.447967Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1/wp_gg_cdn` because it could not be opened.
2025-06-10T12:22:18.448614Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.448898Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.449167Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.449671Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1\wp_gg_folders.ibd' OS error: 103
2025-06-10T12:22:18.450108Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.450378Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.450978Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1/wp_gg_folders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.451515Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1/wp_gg_folders` because it could not be opened.
2025-06-10T12:22:18.452024Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.452278Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.452538Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.453058Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1\wp_gg_galleries.ibd' OS error: 103
2025-06-10T12:22:18.453485Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.453816Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.454213Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1/wp_gg_galleries`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.454914Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1/wp_gg_galleries` because it could not be opened.
2025-06-10T12:22:18.455295Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.455623Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.455903Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.456271Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1\wp_gg_galleries_excluded.ibd' OS error: 103
2025-06-10T12:22:18.456720Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.456981Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.457369Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1/wp_gg_galleries_excluded`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.458027Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1/wp_gg_galleries_excluded` because it could not be opened.
2025-06-10T12:22:18.458408Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.458770Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.459063Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.459430Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1\wp_gg_galleries_resources.ibd' OS error: 103
2025-06-10T12:22:18.459843Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.460092Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.460551Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1/wp_gg_galleries_resources`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.461406Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1/wp_gg_galleries_resources` because it could not be opened.
2025-06-10T12:22:18.462058Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.462327Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.462669Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.463040Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1\wp_gg_image_optimize.ibd' OS error: 103
2025-06-10T12:22:18.463412Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.463779Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.464166Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1/wp_gg_image_optimize`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.464836Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1/wp_gg_image_optimize` because it could not be opened.
2025-06-10T12:22:18.465262Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.465542Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.465889Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.466279Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1\wp_gg_membership_presets.ibd' OS error: 103
2025-06-10T12:22:18.466723Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.466996Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.467414Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1/wp_gg_membership_presets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.468105Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1/wp_gg_membership_presets` because it could not be opened.
2025-06-10T12:22:18.468618Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.468948Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.469240Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.469700Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1\wp_gg_photos.ibd' OS error: 103
2025-06-10T12:22:18.470018Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.470269Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.470730Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1/wp_gg_photos`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.471274Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1/wp_gg_photos` because it could not be opened.
2025-06-10T12:22:18.471707Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.472232Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.472497Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.473063Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1\wp_gg_photos_pos.ibd' OS error: 103
2025-06-10T12:22:18.473478Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.473733Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.474222Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1/wp_gg_photos_pos`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.474980Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1/wp_gg_photos_pos` because it could not be opened.
2025-06-10T12:22:18.475490Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.475774Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.476106Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.476524Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1\wp_gg_photos_settings.ibd' OS error: 103
2025-06-10T12:22:18.476878Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.477157Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.477573Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1/wp_gg_photos_settings`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.478199Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1/wp_gg_photos_settings` because it could not be opened.
2025-06-10T12:22:18.478628Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.478897Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.479280Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.479807Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1\wp_gg_settings_presets.ibd' OS error: 103
2025-06-10T12:22:18.480265Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.480532Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.481175Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1/wp_gg_settings_presets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.481825Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1/wp_gg_settings_presets` because it could not be opened.
2025-06-10T12:22:18.482594Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.482996Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.483470Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.484018Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1\wp_gg_settings_sets.ibd' OS error: 103
2025-06-10T12:22:18.484499Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.484775Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.485362Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1/wp_gg_settings_sets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.485995Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1/wp_gg_settings_sets` because it could not be opened.
2025-06-10T12:22:18.486517Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.486765Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.487158Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.487712Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1\wp_gg_stats.ibd' OS error: 103
2025-06-10T12:22:18.488180Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.488427Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.488819Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1/wp_gg_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.489564Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1/wp_gg_stats` because it could not be opened.
2025-06-10T12:22:18.490047Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.490335Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.490595Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.490983Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1\wp_gg_tags.ibd' OS error: 103
2025-06-10T12:22:18.491336Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.491661Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.492213Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1/wp_gg_tags`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.492742Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1/wp_gg_tags` because it could not be opened.
2025-06-10T12:22:18.493267Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.493514Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.493948Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.494483Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1\wp_links.ibd' OS error: 103
2025-06-10T12:22:18.495041Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.495326Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.495716Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.496355Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1/wp_links` because it could not be opened.
2025-06-10T12:22:18.496708Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.497064Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.497476Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.497939Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1\wp_newsletter.ibd' OS error: 103
2025-06-10T12:22:18.498366Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.498693Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.499297Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1/wp_newsletter`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.499894Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1/wp_newsletter` because it could not be opened.
2025-06-10T12:22:18.500506Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.500883Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.501341Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.501793Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1\wp_newsletter_emails.ibd' OS error: 103
2025-06-10T12:22:18.502304Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.502553Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.503033Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1/wp_newsletter_emails`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.503612Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1/wp_newsletter_emails` because it could not be opened.
2025-06-10T12:22:18.504109Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.504950Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.505281Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.505988Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1\wp_newsletter_sent.ibd' OS error: 103
2025-06-10T12:22:18.506341Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.506843Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.507502Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1/wp_newsletter_sent`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.508122Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1/wp_newsletter_sent` because it could not be opened.
2025-06-10T12:22:18.508573Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.508867Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.509146Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.509637Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1\wp_newsletter_stats.ibd' OS error: 103
2025-06-10T12:22:18.509989Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.510293Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.510792Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1/wp_newsletter_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.511464Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1/wp_newsletter_stats` because it could not be opened.
2025-06-10T12:22:18.512030Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.512421Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.512718Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.513096Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1\wp_newsletter_user_logs.ibd' OS error: 103
2025-06-10T12:22:18.513521Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.513809Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.514332Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1/wp_newsletter_user_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.515035Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1/wp_newsletter_user_logs` because it could not be opened.
2025-06-10T12:22:18.515568Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.515830Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.516090Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.516535Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1\wp_options.ibd' OS error: 103
2025-06-10T12:22:18.516842Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.517255Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.517693Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.518302Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1/wp_options` because it could not be opened.
2025-06-10T12:22:18.518990Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.519311Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.519584Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.519951Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1\wp_post_views.ibd' OS error: 103
2025-06-10T12:22:18.520369Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.520632Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.521027Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1/wp_post_views`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.521677Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1/wp_post_views` because it could not be opened.
2025-06-10T12:22:18.522045Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.522392Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.522652Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.523061Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:18.523474Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.523722Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.524109Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.524709Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1/wp_postmeta` because it could not be opened.
2025-06-10T12:22:18.525058Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.525456Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.525729Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.526091Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1\wp_posts.ibd' OS error: 103
2025-06-10T12:22:18.526452Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.526704Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.527094Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.527690Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1/wp_posts` because it could not be opened.
2025-06-10T12:22:18.528067Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.528420Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.528677Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.529087Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1\wp_revslider_css.ibd' OS error: 103
2025-06-10T12:22:18.529492Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.529741Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.530133Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1/wp_revslider_css`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.530882Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1/wp_revslider_css` because it could not be opened.
2025-06-10T12:22:18.531337Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.531603Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.531872Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.532310Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1\wp_revslider_css_bkp.ibd' OS error: 103
2025-06-10T12:22:18.532764Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.533064Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.533553Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1/wp_revslider_css_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.534119Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1/wp_revslider_css_bkp` because it could not be opened.
2025-06-10T12:22:18.534665Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.534925Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.535250Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.535636Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1\wp_revslider_layer_animations.ibd' OS error: 103
2025-06-10T12:22:18.535972Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.536394Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.536950Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1/wp_revslider_layer_animations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.537745Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1/wp_revslider_layer_animations` because it could not be opened.
2025-06-10T12:22:18.538241Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.538621Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.539296Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.539688Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1\wp_revslider_layer_animations_bkp.ibd' OS error: 103
2025-06-10T12:22:18.540154Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.540420Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.540839Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1/wp_revslider_layer_animations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.541792Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1/wp_revslider_layer_animations_bkp` because it could not be opened.
2025-06-10T12:22:18.542315Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.542587Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.542860Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.543301Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1\wp_revslider_navigations.ibd' OS error: 103
2025-06-10T12:22:18.543651Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.543915Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.544415Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1/wp_revslider_navigations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.545073Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1/wp_revslider_navigations` because it could not be opened.
2025-06-10T12:22:18.545600Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.545872Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.546306Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.546868Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1\wp_revslider_navigations_bkp.ibd' OS error: 103
2025-06-10T12:22:18.547462Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.547826Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.548340Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1/wp_revslider_navigations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.548916Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1/wp_revslider_navigations_bkp` because it could not be opened.
2025-06-10T12:22:18.549451Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.549711Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.549969Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.550446Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1\wp_revslider_sliders.ibd' OS error: 103
2025-06-10T12:22:18.550775Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.551198Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.551604Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1/wp_revslider_sliders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.552267Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1/wp_revslider_sliders` because it could not be opened.
2025-06-10T12:22:18.552681Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.552953Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.553378Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.553789Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1\wp_revslider_sliders_bkp.ibd' OS error: 103
2025-06-10T12:22:18.554201Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.554455Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.554847Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1/wp_revslider_sliders_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.555542Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1/wp_revslider_sliders_bkp` because it could not be opened.
2025-06-10T12:22:18.555943Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.556281Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.556540Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.556900Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1\wp_revslider_slides.ibd' OS error: 103
2025-06-10T12:22:18.557379Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.557715Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.558403Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1/wp_revslider_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.559188Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1/wp_revslider_slides` because it could not be opened.
2025-06-10T12:22:18.559652Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.560129Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.560421Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.560793Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1\wp_revslider_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:18.561283Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.561586Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.562029Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1/wp_revslider_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.562627Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1/wp_revslider_slides_bkp` because it could not be opened.
2025-06-10T12:22:18.563121Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.563422Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.563676Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.564132Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1\wp_revslider_static_slides.ibd' OS error: 103
2025-06-10T12:22:18.564522Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.564774Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.565239Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1/wp_revslider_static_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.565800Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1/wp_revslider_static_slides` because it could not be opened.
2025-06-10T12:22:18.566447Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.566698Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.566951Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.567559Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1\wp_revslider_static_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:18.567935Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.568377Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.568845Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1/wp_revslider_static_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.570237Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1/wp_revslider_static_slides_bkp` because it could not be opened.
2025-06-10T12:22:18.571252Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.571659Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.571982Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.572371Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:18.572747Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.573039Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.573446Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.574104Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:18.574582Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.575122Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.575424Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.575816Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:18.576179Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.576446Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.576892Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.577706Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:18.578215Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.578516Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.578796Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.579247Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:18.579560Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.579806Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.580336Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.580890Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1/wp_termmeta` because it could not be opened.
2025-06-10T12:22:18.581366Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.581620Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.581878Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.582405Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1\wp_terms.ibd' OS error: 103
2025-06-10T12:22:18.582728Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.583006Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.583423Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.584009Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1/wp_terms` because it could not be opened.
2025-06-10T12:22:18.584374Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.584637Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.584921Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.585322Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:18.585646Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.585920Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.586362Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.586954Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1/wp_usermeta` because it could not be opened.
2025-06-10T12:22:18.587321Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.587583Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.587854Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.588303Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1\wp_users.ibd' OS error: 103
2025-06-10T12:22:18.588624Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.588900Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.589316Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.589879Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1/wp_users` because it could not be opened.
2025-06-10T12:22:18.590290Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.590630Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.590917Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.591302Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1\wp_wpfm_backup.ibd' OS error: 103
2025-06-10T12:22:18.591636Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.591922Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.592347Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1/wp_wpfm_backup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.592973Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1/wp_wpfm_backup` because it could not be opened.
2025-06-10T12:22:18.593366Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.593628Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.593935Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.594362Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1\wp_yoast_seo_links.ibd' OS error: 103
2025-06-10T12:22:18.594705Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.594985Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.595404Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1/wp_yoast_seo_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.596021Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1/wp_yoast_seo_links` because it could not be opened.
2025-06-10T12:22:18.596428Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.596695Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.597040Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.597482Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1\wp_yoast_seo_meta.ibd' OS error: 103
2025-06-10T12:22:18.597920Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.598195Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.598592Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1/wp_yoast_seo_meta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.599200Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1/wp_yoast_seo_meta` because it could not be opened.
2025-06-10T12:22:18.600049Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.600353Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.600918Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.602300Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_actionscheduler_actions.ibd' OS error: 103
2025-06-10T12:22:18.602666Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.603436Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.603864Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_actionscheduler_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.604456Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_actionscheduler_actions` because it could not be opened.
2025-06-10T12:22:18.604977Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.605241Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.605511Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.605954Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_actionscheduler_claims.ibd' OS error: 103
2025-06-10T12:22:18.606308Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.606564Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.607041Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_actionscheduler_claims`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.607637Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_actionscheduler_claims` because it could not be opened.
2025-06-10T12:22:18.608550Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.609180Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.609681Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.610577Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_actionscheduler_groups.ibd' OS error: 103
2025-06-10T12:22:18.611338Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.611658Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.612197Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_actionscheduler_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.612846Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_actionscheduler_groups` because it could not be opened.
2025-06-10T12:22:18.613271Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.613520Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.613951Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.614319Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_actionscheduler_logs.ibd' OS error: 103
2025-06-10T12:22:18.614653Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.614980Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.615662Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_actionscheduler_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.616282Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_actionscheduler_logs` because it could not be opened.
2025-06-10T12:22:18.616733Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.617028Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.617289Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.617653Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:18.618040Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.618309Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.618774Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.619364Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:18.619809Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.620069Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.620331Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.620749Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_comments.ibd' OS error: 103
2025-06-10T12:22:18.621103Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.621368Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.621809Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.622377Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_comments` because it could not be opened.
2025-06-10T12:22:18.622791Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.623070Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.623354Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.623792Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_csshero4.ibd' OS error: 103
2025-06-10T12:22:18.624151Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.624418Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.624869Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_csshero4`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.625446Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_csshero4` because it could not be opened.
2025-06-10T12:22:18.626077Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.626349Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.626625Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.627077Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:18.627401Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.627682Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.628152Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.628750Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_fbv` because it could not be opened.
2025-06-10T12:22:18.629159Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.629430Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.629738Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.630118Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:18.630494Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.630795Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.631205Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.631905Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:18.632726Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.632997Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.633327Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.633715Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_gg_attributes.ibd' OS error: 103
2025-06-10T12:22:18.634091Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.634426Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.634978Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_gg_attributes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.635649Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_gg_attributes` because it could not be opened.
2025-06-10T12:22:18.636167Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.636423Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.636684Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.637153Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_gg_cdn.ibd' OS error: 103
2025-06-10T12:22:18.637465Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.637713Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.638183Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_gg_cdn`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.638716Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_gg_cdn` because it could not be opened.
2025-06-10T12:22:18.639326Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.639653Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.640046Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.640432Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_gg_folders.ibd' OS error: 103
2025-06-10T12:22:18.640764Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.641090Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.641499Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_gg_folders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.642358Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_gg_folders` because it could not be opened.
2025-06-10T12:22:18.642844Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.643161Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.643417Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.643775Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_gg_galleries.ibd' OS error: 103
2025-06-10T12:22:18.644221Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.644511Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.644948Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_gg_galleries`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.645505Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_gg_galleries` because it could not be opened.
2025-06-10T12:22:18.645977Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.646236Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.646492Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.646907Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_gg_galleries_excluded.ibd' OS error: 103
2025-06-10T12:22:18.647297Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.647542Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.647997Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_gg_galleries_excluded`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.648713Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_gg_galleries_excluded` because it could not be opened.
2025-06-10T12:22:18.649185Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.649436Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.649690Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.650157Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_gg_galleries_resources.ibd' OS error: 103
2025-06-10T12:22:18.650485Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.650726Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.651206Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_gg_galleries_resources`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.651757Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_gg_galleries_resources` because it could not be opened.
2025-06-10T12:22:18.652301Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.652551Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.652807Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.653279Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_gg_image_optimize.ibd' OS error: 103
2025-06-10T12:22:18.653609Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.653968Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.654455Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_gg_image_optimize`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.655188Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_gg_image_optimize` because it could not be opened.
2025-06-10T12:22:18.655716Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.656015Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.656272Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.656635Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_gg_membership_presets.ibd' OS error: 103
2025-06-10T12:22:18.657976Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.658325Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.658724Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_gg_membership_presets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.659428Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_gg_membership_presets` because it could not be opened.
2025-06-10T12:22:18.659927Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.660208Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.660459Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.660864Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_gg_photos.ibd' OS error: 103
2025-06-10T12:22:18.661211Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.661654Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.662297Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_gg_photos`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.662914Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_gg_photos` because it could not be opened.
2025-06-10T12:22:18.663375Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.663625Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.664029Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.664451Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_gg_photos_pos.ibd' OS error: 103
2025-06-10T12:22:18.664801Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.665120Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.665499Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_gg_photos_pos`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.666218Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_gg_photos_pos` because it could not be opened.
2025-06-10T12:22:18.666637Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.666990Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.667246Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.667690Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_gg_photos_settings.ibd' OS error: 103
2025-06-10T12:22:18.668164Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.668416Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.668895Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_gg_photos_settings`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.669565Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_gg_photos_settings` because it could not be opened.
2025-06-10T12:22:18.670165Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.670414Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.670671Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.671137Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_gg_settings_presets.ibd' OS error: 103
2025-06-10T12:22:18.671469Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.671715Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.672246Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_gg_settings_presets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.672835Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_gg_settings_presets` because it could not be opened.
2025-06-10T12:22:18.673229Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.673479Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.673869Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.674520Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_gg_settings_sets.ibd' OS error: 103
2025-06-10T12:22:18.675064Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.675404Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.675881Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_gg_settings_sets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.676532Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_gg_settings_sets` because it could not be opened.
2025-06-10T12:22:18.677055Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.677328Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.677599Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.678065Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_gg_stats.ibd' OS error: 103
2025-06-10T12:22:18.678375Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.678627Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.679093Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_gg_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.679623Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_gg_stats` because it could not be opened.
2025-06-10T12:22:18.680340Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.680598Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.681107Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.681976Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_gg_tags.ibd' OS error: 103
2025-06-10T12:22:18.682386Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.683004Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.683453Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_gg_tags`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.684062Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_gg_tags` because it could not be opened.
2025-06-10T12:22:18.684611Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.684866Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.685125Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.685558Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_links.ibd' OS error: 103
2025-06-10T12:22:18.686108Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.686410Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.686895Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.687485Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_links` because it could not be opened.
2025-06-10T12:22:18.688705Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.689060Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.689340Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.689789Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_options.ibd' OS error: 103
2025-06-10T12:22:18.690132Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.690407Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.690897Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.691675Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_options` because it could not be opened.
2025-06-10T12:22:18.692094Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.692363Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.692697Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.693082Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_post_views.ibd' OS error: 103
2025-06-10T12:22:18.693404Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.693704Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.694134Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_post_views`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.694745Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_post_views` because it could not be opened.
2025-06-10T12:22:18.695665Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.695943Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.696211Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.696640Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:18.696967Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.697219Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.697720Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.698256Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_postmeta` because it could not be opened.
2025-06-10T12:22:18.698689Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.698945Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.699202Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.699628Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_postmeta_backup.ibd' OS error: 103
2025-06-10T12:22:18.699954Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.700205Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.700695Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_postmeta_backup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.701341Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_postmeta_backup` because it could not be opened.
2025-06-10T12:22:18.701872Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.702120Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.702375Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.702829Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_posts.ibd' OS error: 103
2025-06-10T12:22:18.703131Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.703376Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.703876Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.704429Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_posts` because it could not be opened.
2025-06-10T12:22:18.704850Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.705098Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.705352Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.705788Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_redirection_404.ibd' OS error: 103
2025-06-10T12:22:18.706112Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.706355Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.706871Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_redirection_404`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.707649Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_redirection_404` because it could not be opened.
2025-06-10T12:22:18.708062Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.708315Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.708691Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.709090Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_redirection_groups.ibd' OS error: 103
2025-06-10T12:22:18.709617Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.709878Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.710266Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_redirection_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.710887Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_redirection_groups` because it could not be opened.
2025-06-10T12:22:18.711297Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.711614Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.711941Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.712325Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_redirection_items.ibd' OS error: 103
2025-06-10T12:22:18.712723Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.713070Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.713476Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_redirection_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.714195Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_redirection_items` because it could not be opened.
2025-06-10T12:22:18.715099Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.715413Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.715718Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.716298Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_redirection_logs.ibd' OS error: 103
2025-06-10T12:22:18.716645Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.717028Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.717471Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_redirection_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.718125Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_redirection_logs` because it could not be opened.
2025-06-10T12:22:18.718639Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.718982Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.719313Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.719678Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_revslider_css.ibd' OS error: 103
2025-06-10T12:22:18.720090Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.720349Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.720747Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_revslider_css`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.721516Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_revslider_css` because it could not be opened.
2025-06-10T12:22:18.722096Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.722405Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.722742Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.723228Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_revslider_css_bkp.ibd' OS error: 103
2025-06-10T12:22:18.723578Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.723914Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.724326Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_revslider_css_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.724969Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_revslider_css_bkp` because it could not be opened.
2025-06-10T12:22:18.725390Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.725645Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.725969Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.726337Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_revslider_layer_animations.ibd' OS error: 103
2025-06-10T12:22:18.726694Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.727026Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.727459Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_revslider_layer_animations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.728166Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_revslider_layer_animations` because it could not be opened.
2025-06-10T12:22:18.728564Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.728864Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.729144Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.729505Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_revslider_layer_animations_bkp.ibd' OS error: 103
2025-06-10T12:22:18.729976Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.730243Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.730642Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_revslider_layer_animations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.731296Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_revslider_layer_animations_bkp` because it could not be opened.
2025-06-10T12:22:18.731702Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.732034Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.732295Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.732655Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_revslider_navigations.ibd' OS error: 103
2025-06-10T12:22:18.733059Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.733330Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.733748Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_revslider_navigations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.734430Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_revslider_navigations` because it could not be opened.
2025-06-10T12:22:18.734866Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.735135Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.735398Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.735808Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_revslider_navigations_bkp.ibd' OS error: 103
2025-06-10T12:22:18.736208Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.736475Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.736933Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_revslider_navigations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.737518Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_revslider_navigations_bkp` because it could not be opened.
2025-06-10T12:22:18.738133Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.738402Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.738675Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.739090Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_revslider_sliders.ibd' OS error: 103
2025-06-10T12:22:18.739437Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.739701Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.740148Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_revslider_sliders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.740858Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_revslider_sliders` because it could not be opened.
2025-06-10T12:22:18.741327Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.741582Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.741893Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.742277Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_revslider_sliders_bkp.ibd' OS error: 103
2025-06-10T12:22:18.742618Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.742926Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.743318Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_revslider_sliders_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.744054Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_revslider_sliders_bkp` because it could not be opened.
2025-06-10T12:22:18.744725Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.745019Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.745477Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.745879Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_revslider_slides.ibd' OS error: 103
2025-06-10T12:22:18.746442Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.746708Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.747190Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_revslider_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.748092Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_revslider_slides` because it could not be opened.
2025-06-10T12:22:18.748657Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.748980Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.749253Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.749662Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_revslider_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:18.750155Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.750439Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.750908Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_revslider_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.751494Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_revslider_slides_bkp` because it could not be opened.
2025-06-10T12:22:18.752189Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.752460Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.752725Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.753236Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_revslider_static_slides.ibd' OS error: 103
2025-06-10T12:22:18.753589Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.754179Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.754649Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_revslider_static_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.755337Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_revslider_static_slides` because it could not be opened.
2025-06-10T12:22:18.755863Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.756169Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.756426Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.756876Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_revslider_static_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:18.757272Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.757520Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.757969Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_revslider_static_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.758542Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_revslider_static_slides_bkp` because it could not be opened.
2025-06-10T12:22:18.759031Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.759280Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.759535Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.759989Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_rich_web_icons.ibd' OS error: 103
2025-06-10T12:22:18.760310Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.760558Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.761058Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_rich_web_icons`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.761723Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_rich_web_icons` because it could not be opened.
2025-06-10T12:22:18.762181Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.762437Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.762793Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.763201Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_rich_web_timeline_manager.ibd' OS error: 103
2025-06-10T12:22:18.763557Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.763983Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.764439Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_rich_web_timeline_manager`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.765138Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_rich_web_timeline_manager` because it could not be opened.
2025-06-10T12:22:18.765569Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.765909Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.766167Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.766542Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_rich_web_timeline_options.ibd' OS error: 103
2025-06-10T12:22:18.767009Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.767271Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.767753Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_rich_web_timeline_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.768360Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_rich_web_timeline_options` because it could not be opened.
2025-06-10T12:22:18.769115Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.769393Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.769657Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.770092Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_rich_web_timeline_short_options.ibd' OS error: 103
2025-06-10T12:22:18.770474Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.770771Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.771187Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_rich_web_timeline_short_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.771841Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_rich_web_timeline_short_options` because it could not be opened.
2025-06-10T12:22:18.772327Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.772653Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.773037Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.773401Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_rich_web_timeline_style_options.ibd' OS error: 103
2025-06-10T12:22:18.773971Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.774255Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.774658Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_rich_web_timeline_style_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.775396Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_rich_web_timeline_style_options` because it could not be opened.
2025-06-10T12:22:18.776135Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.776804Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.777073Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.778173Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_rich_web_timeline_style_options_2.ibd' OS error: 103
2025-06-10T12:22:18.778538Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.778921Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.779499Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_rich_web_timeline_style_options_2`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.780230Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_rich_web_timeline_style_options_2` because it could not be opened.
2025-06-10T12:22:18.780778Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.781091Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.781354Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.782020Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_sbi_instagram_feed_locator.ibd' OS error: 103
2025-06-10T12:22:18.782417Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.782732Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.783149Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_sbi_instagram_feed_locator`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.783823Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_sbi_instagram_feed_locator` because it could not be opened.
2025-06-10T12:22:18.784371Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.784677Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.784951Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.785420Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_sbi_instagram_feeds_posts.ibd' OS error: 103
2025-06-10T12:22:18.785883Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.786201Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.786660Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_sbi_instagram_feeds_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.787272Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_sbi_instagram_feeds_posts` because it could not be opened.
2025-06-10T12:22:18.787862Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.788396Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.788709Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.789097Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_sbi_instagram_posts.ibd' OS error: 103
2025-06-10T12:22:18.789452Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.789770Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.790182Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_sbi_instagram_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.790840Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_sbi_instagram_posts` because it could not be opened.
2025-06-10T12:22:18.791267Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.791601Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.791876Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.792257Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:18.792675Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.792937Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.793329Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.793985Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:18.794492Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.794847Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.795159Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.795568Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:18.795959Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.796205Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.796691Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.797256Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:18.797779Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.798032Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.798286Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.798779Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:18.799092Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.799342Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.799862Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.800496Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_termmeta` because it could not be opened.
2025-06-10T12:22:18.801176Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.801632Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.801934Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.802316Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_terms.ibd' OS error: 103
2025-06-10T12:22:18.802670Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.802932Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.803351Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.803953Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_terms` because it could not be opened.
2025-06-10T12:22:18.804392Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.804820Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.805148Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.805633Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:18.805948Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.806256Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.806726Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.807453Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_usermeta` because it could not be opened.
2025-06-10T12:22:18.808335Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.808813Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.810710Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.811114Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_users.ibd' OS error: 103
2025-06-10T12:22:18.811459Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.811755Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.812187Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.812846Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_users` because it could not be opened.
2025-06-10T12:22:18.813276Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.813679Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.813953Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.814339Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_wc_admin_note_actions.ibd' OS error: 103
2025-06-10T12:22:18.814777Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.815284Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.815788Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_wc_admin_note_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.816373Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_wc_admin_note_actions` because it could not be opened.
2025-06-10T12:22:18.816981Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.817247Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.817520Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.818137Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_wc_admin_notes.ibd' OS error: 103
2025-06-10T12:22:18.818480Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.818785Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.819174Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_wc_admin_notes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.819871Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_wc_admin_notes` because it could not be opened.
2025-06-10T12:22:18.820279Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.820651Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.820941Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.821680Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_wc_category_lookup.ibd' OS error: 103
2025-06-10T12:22:18.822033Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.822277Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.822813Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_wc_category_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.823351Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_wc_category_lookup` because it could not be opened.
2025-06-10T12:22:18.823816Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.824061Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.824317Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.824789Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_wc_customer_lookup.ibd' OS error: 103
2025-06-10T12:22:18.825124Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.825363Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.825976Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_wc_customer_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.826783Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_wc_customer_lookup` because it could not be opened.
2025-06-10T12:22:18.827202Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.827448Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.827818Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.828192Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_wc_download_log.ibd' OS error: 103
2025-06-10T12:22:18.828636Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.829000Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.829400Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_wc_download_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.829958Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_wc_download_log` because it could not be opened.
2025-06-10T12:22:18.830333Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.830694Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.830961Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.831319Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_wc_order_coupon_lookup.ibd' OS error: 103
2025-06-10T12:22:18.831756Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.832006Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.832391Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_wc_order_coupon_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.833045Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_wc_order_coupon_lookup` because it could not be opened.
2025-06-10T12:22:18.833427Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.833760Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.834153Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.834555Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_wc_order_product_lookup.ibd' OS error: 103
2025-06-10T12:22:18.834915Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.835179Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.835640Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_wc_order_product_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.836242Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_wc_order_product_lookup` because it could not be opened.
2025-06-10T12:22:18.836761Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.837014Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.837271Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.837777Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_wc_order_stats.ibd' OS error: 103
2025-06-10T12:22:18.838106Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.838353Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.838829Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_wc_order_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.839380Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_wc_order_stats` because it could not be opened.
2025-06-10T12:22:18.839879Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.840577Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.841086Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.841635Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_wc_order_tax_lookup.ibd' OS error: 103
2025-06-10T12:22:18.842372Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.842659Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.843163Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_wc_order_tax_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.843858Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_wc_order_tax_lookup` because it could not be opened.
2025-06-10T12:22:18.844334Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.844590Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.844895Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.845288Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_wc_product_meta_lookup.ibd' OS error: 103
2025-06-10T12:22:18.845633Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.845931Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.846348Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_wc_product_meta_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.847032Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_wc_product_meta_lookup` because it could not be opened.
2025-06-10T12:22:18.847483Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.848029Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.848311Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.848683Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_wc_reserved_stock.ibd' OS error: 103
2025-06-10T12:22:18.849091Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.849347Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.849751Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_wc_reserved_stock`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.850546Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_wc_reserved_stock` because it could not be opened.
2025-06-10T12:22:18.851143Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.851402Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.851655Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.852115Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_wc_tax_rate_classes.ibd' OS error: 103
2025-06-10T12:22:18.852437Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.852676Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.853186Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_wc_tax_rate_classes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.853739Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_wc_tax_rate_classes` because it could not be opened.
2025-06-10T12:22:18.854190Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.854440Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.854700Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.855133Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_wc_webhooks.ibd' OS error: 103
2025-06-10T12:22:18.855453Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.855698Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.856144Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_wc_webhooks`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.856686Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_wc_webhooks` because it could not be opened.
2025-06-10T12:22:18.857121Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.857390Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.857678Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.858132Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_woocommerce_api_keys.ibd' OS error: 103
2025-06-10T12:22:18.858463Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.858710Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.859164Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_woocommerce_api_keys`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.859723Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_woocommerce_api_keys` because it could not be opened.
2025-06-10T12:22:18.860252Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.860514Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.860770Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.861214Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_woocommerce_attribute_taxonomies.ibd' OS error: 103
2025-06-10T12:22:18.861574Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.861869Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.862275Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_woocommerce_attribute_taxonomies`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.862927Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_woocommerce_attribute_taxonomies` because it could not be opened.
2025-06-10T12:22:18.863405Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.863659Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.863975Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.864331Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_woocommerce_downloadable_product_permissions.ibd' OS error: 103
2025-06-10T12:22:18.864717Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.865055Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.865440Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_woocommerce_downloadable_product_permissions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.866179Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_woocommerce_downloadable_product_permissions` because it could not be opened.
2025-06-10T12:22:18.866610Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.866910Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.867179Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.867549Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_woocommerce_log.ibd' OS error: 103
2025-06-10T12:22:18.867933Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.868186Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.868618Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_woocommerce_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.869270Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_woocommerce_log` because it could not be opened.
2025-06-10T12:22:18.869678Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.870024Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.870273Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.870630Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_woocommerce_order_itemmeta.ibd' OS error: 103
2025-06-10T12:22:18.871040Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.871289Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.871717Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_woocommerce_order_itemmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.872592Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_woocommerce_order_itemmeta` because it could not be opened.
2025-06-10T12:22:18.872990Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.873488Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.873740Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.874222Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_woocommerce_order_items.ibd' OS error: 103
2025-06-10T12:22:18.874691Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.874957Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.875447Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_woocommerce_order_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.876100Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_woocommerce_order_items` because it could not be opened.
2025-06-10T12:22:18.876541Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.876805Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.877104Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.877481Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_woocommerce_payment_tokenmeta.ibd' OS error: 103
2025-06-10T12:22:18.877850Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.878163Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.878611Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_woocommerce_payment_tokenmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.879264Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_woocommerce_payment_tokenmeta` because it could not be opened.
2025-06-10T12:22:18.879745Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.880081Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.880381Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.880921Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_woocommerce_payment_tokens.ibd' OS error: 103
2025-06-10T12:22:18.881383Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.881662Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.882163Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_woocommerce_payment_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.882791Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_woocommerce_payment_tokens` because it could not be opened.
2025-06-10T12:22:18.883449Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.883707Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.883976Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.884468Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_woocommerce_sessions.ibd' OS error: 103
2025-06-10T12:22:18.884819Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.885120Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.885526Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_woocommerce_sessions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.886147Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_woocommerce_sessions` because it could not be opened.
2025-06-10T12:22:18.886561Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.886827Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.887291Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.887707Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_woocommerce_shipping_zone_locations.ibd' OS error: 103
2025-06-10T12:22:18.888220Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.888490Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.888889Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_woocommerce_shipping_zone_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.889554Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_woocommerce_shipping_zone_locations` because it could not be opened.
2025-06-10T12:22:18.890054Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.890335Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.890595Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.891006Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_woocommerce_shipping_zone_methods.ibd' OS error: 103
2025-06-10T12:22:18.891495Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.891749Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.892213Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_woocommerce_shipping_zone_methods`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.892803Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_woocommerce_shipping_zone_methods` because it could not be opened.
2025-06-10T12:22:18.893364Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.893620Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.894008Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.894473Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_woocommerce_shipping_zones.ibd' OS error: 103
2025-06-10T12:22:18.894825Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.895218Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.895615Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_woocommerce_shipping_zones`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.896302Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_woocommerce_shipping_zones` because it could not be opened.
2025-06-10T12:22:18.896972Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.897373Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.897638Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.898139Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_woocommerce_tax_rate_locations.ibd' OS error: 103
2025-06-10T12:22:18.898530Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.898782Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.899276Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_woocommerce_tax_rate_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.899915Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_woocommerce_tax_rate_locations` because it could not be opened.
2025-06-10T12:22:18.900418Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.900678Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.901032Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.901504Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_woocommerce_tax_rates.ibd' OS error: 103
2025-06-10T12:22:18.901847Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.902219Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.902736Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_woocommerce_tax_rates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.903353Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_woocommerce_tax_rates` because it could not be opened.
2025-06-10T12:22:18.903759Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.904113Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.904432Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.905050Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_wpgmza.ibd' OS error: 103
2025-06-10T12:22:18.905721Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.905968Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.906692Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_wpgmza`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.907639Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_wpgmza` because it could not be opened.
2025-06-10T12:22:18.908186Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.908462Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.908758Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.909151Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_wpgmza_circles.ibd' OS error: 103
2025-06-10T12:22:18.909502Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.909767Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.910218Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_wpgmza_circles`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.910800Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_wpgmza_circles` because it could not be opened.
2025-06-10T12:22:18.911447Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.911716Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.911979Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.912435Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_wpgmza_maps.ibd' OS error: 103
2025-06-10T12:22:18.912763Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.913020Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.913571Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_wpgmza_maps`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.914311Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_wpgmza_maps` because it could not be opened.
2025-06-10T12:22:18.914791Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.915045Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.915374Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.915740Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_wpgmza_polygon.ibd' OS error: 103
2025-06-10T12:22:18.916072Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.916389Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.916781Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_wpgmza_polygon`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.917423Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_wpgmza_polygon` because it could not be opened.
2025-06-10T12:22:18.917860Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.918141Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.918535Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.918939Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_wpgmza_polylines.ibd' OS error: 103
2025-06-10T12:22:18.919351Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.919600Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.919994Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_wpgmza_polylines`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.920694Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_wpgmza_polylines` because it could not be opened.
2025-06-10T12:22:18.921080Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.921389Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.921646Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.922153Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_wpgmza_rectangles.ibd' OS error: 103
2025-06-10T12:22:18.922530Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.922785Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.923266Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_wpgmza_rectangles`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.923818Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_wpgmza_rectangles` because it could not be opened.
2025-06-10T12:22:18.924326Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.924576Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.924830Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.925286Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:18.925622Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.925869Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.926353Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.926895Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:18.927359Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.927601Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.927850Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.928310Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:18.928616Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.928857Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.929349Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.929868Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:18.930313Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.930552Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.930801Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.931281Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:18.931647Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.931890Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.932504Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.933121Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:18.933681Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.933954Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.934297Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.934656Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem10\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:18.934993Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.935455Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.936115Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem10/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.936890Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem10/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:18.937403Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.937653Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.937907Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.938432Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_actionscheduler_actions.ibd' OS error: 103
2025-06-10T12:22:18.938809Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.939466Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.939880Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_actionscheduler_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.940552Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_actionscheduler_actions` because it could not be opened.
2025-06-10T12:22:18.940959Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.941323Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.941585Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.941945Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_actionscheduler_claims.ibd' OS error: 103
2025-06-10T12:22:18.942388Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.942651Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.943056Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_actionscheduler_claims`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.943675Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_actionscheduler_claims` because it could not be opened.
2025-06-10T12:22:18.944120Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.944392Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.944650Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.945022Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_actionscheduler_groups.ibd' OS error: 103
2025-06-10T12:22:18.945455Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.945704Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.946346Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_actionscheduler_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.946927Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_actionscheduler_groups` because it could not be opened.
2025-06-10T12:22:18.947408Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.947654Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.947906Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.948339Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_actionscheduler_logs.ibd' OS error: 103
2025-06-10T12:22:18.948673Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.948979Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.949873Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_actionscheduler_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.950527Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_actionscheduler_logs` because it could not be opened.
2025-06-10T12:22:18.950941Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.951405Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.951744Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.952359Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:18.952840Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.953248Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.953950Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.955724Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:18.956233Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.956503Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.956793Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.957209Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_comments.ibd' OS error: 103
2025-06-10T12:22:18.957538Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.957798Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.958252Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.958825Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_comments` because it could not be opened.
2025-06-10T12:22:18.959480Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.959763Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.960030Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.960491Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_csshero4.ibd' OS error: 103
2025-06-10T12:22:18.960812Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.961083Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.961626Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_csshero4`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.962324Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_csshero4` because it could not be opened.
2025-06-10T12:22:18.962791Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.963150Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.963461Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.963827Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:18.964206Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.964475Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.964867Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.965588Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_fbv` because it could not be opened.
2025-06-10T12:22:18.966202Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.966665Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.966970Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.967530Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:18.967884Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.968367Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.969121Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.969855Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:18.970504Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.970784Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.971069Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.971525Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_gg_attributes.ibd' OS error: 103
2025-06-10T12:22:18.971853Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.972182Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.972622Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_gg_attributes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.973239Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_gg_attributes` because it could not be opened.
2025-06-10T12:22:18.973627Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.973945Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.974385Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.974767Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_gg_cdn.ibd' OS error: 103
2025-06-10T12:22:18.975151Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.975423Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.975837Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_gg_cdn`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.976427Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_gg_cdn` because it could not be opened.
2025-06-10T12:22:18.976796Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.977075Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.977370Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.977736Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_gg_folders.ibd' OS error: 103
2025-06-10T12:22:18.978087Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.978390Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.978796Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_gg_folders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.979658Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_gg_folders` because it could not be opened.
2025-06-10T12:22:18.980219Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.980483Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.980748Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.981228Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_gg_galleries.ibd' OS error: 103
2025-06-10T12:22:18.981548Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.981804Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.982308Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_gg_galleries`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.982888Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_gg_galleries` because it could not be opened.
2025-06-10T12:22:18.983398Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.983649Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.983904Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.985014Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_gg_galleries_excluded.ibd' OS error: 103
2025-06-10T12:22:18.985416Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.985847Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.986259Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_gg_galleries_excluded`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.987056Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_gg_galleries_excluded` because it could not be opened.
2025-06-10T12:22:18.987548Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.987827Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.988097Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.988467Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_gg_galleries_resources.ibd' OS error: 103
2025-06-10T12:22:18.988948Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.989219Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.989708Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_gg_galleries_resources`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.990299Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_gg_galleries_resources` because it could not be opened.
2025-06-10T12:22:18.990807Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.991060Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.991320Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.991795Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_gg_image_optimize.ibd' OS error: 103
2025-06-10T12:22:18.992127Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.992376Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.992893Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_gg_image_optimize`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.993455Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_gg_image_optimize` because it could not be opened.
2025-06-10T12:22:18.994291Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.994717Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.995077Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.995557Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_gg_membership_presets.ibd' OS error: 103
2025-06-10T12:22:18.995907Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.996158Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.996634Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_gg_membership_presets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:18.997260Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_gg_membership_presets` because it could not be opened.
2025-06-10T12:22:18.997782Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:18.998121Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:18.998376Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:18.998846Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_gg_photos.ibd' OS error: 103
2025-06-10T12:22:18.999202Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:18.999493Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:18.999981Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_gg_photos`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.000569Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_gg_photos` because it could not be opened.
2025-06-10T12:22:19.000967Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.001326Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.001689Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.002101Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_gg_photos_pos.ibd' OS error: 103
2025-06-10T12:22:19.002425Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.002753Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.003138Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_gg_photos_pos`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.003788Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_gg_photos_pos` because it could not be opened.
2025-06-10T12:22:19.004376Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.004792Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.005046Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.005396Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_gg_photos_settings.ibd' OS error: 103
2025-06-10T12:22:19.005801Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.006045Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.006424Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_gg_photos_settings`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.007076Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_gg_photos_settings` because it could not be opened.
2025-06-10T12:22:19.007508Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.007872Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.008145Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.008543Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_gg_settings_presets.ibd' OS error: 103
2025-06-10T12:22:19.008926Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.009169Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.009634Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_gg_settings_presets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.010204Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_gg_settings_presets` because it could not be opened.
2025-06-10T12:22:19.010706Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.010954Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.011207Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.011730Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_gg_settings_sets.ibd' OS error: 103
2025-06-10T12:22:19.012108Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.012662Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.013192Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_gg_settings_sets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.013952Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_gg_settings_sets` because it could not be opened.
2025-06-10T12:22:19.014669Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.014975Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.015234Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.015774Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_gg_stats.ibd' OS error: 103
2025-06-10T12:22:19.016484Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.016751Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.017247Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_gg_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.018006Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_gg_stats` because it could not be opened.
2025-06-10T12:22:19.018766Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.019038Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.019342Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.019746Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_gg_tags.ibd' OS error: 103
2025-06-10T12:22:19.020106Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.020368Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.020801Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_gg_tags`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.021363Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_gg_tags` because it could not be opened.
2025-06-10T12:22:19.021824Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.022126Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.022407Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.022841Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_links.ibd' OS error: 103
2025-06-10T12:22:19.023173Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.023442Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.023904Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.024469Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_links` because it could not be opened.
2025-06-10T12:22:19.025461Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.025967Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.026437Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.027060Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_options.ibd' OS error: 103
2025-06-10T12:22:19.027608Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.028133Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.028618Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.029245Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_options` because it could not be opened.
2025-06-10T12:22:19.029674Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.029943Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.030202Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.030622Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_post_views.ibd' OS error: 103
2025-06-10T12:22:19.030957Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.031208Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.031672Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_post_views`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.032260Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_post_views` because it could not be opened.
2025-06-10T12:22:19.032748Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.033001Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.033260Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.033715Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:19.034162Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.034418Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.034906Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.035435Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_postmeta` because it could not be opened.
2025-06-10T12:22:19.035980Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.036232Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.036485Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.037018Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_posts.ibd' OS error: 103
2025-06-10T12:22:19.037368Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.037663Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.038057Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.038644Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_posts` because it could not be opened.
2025-06-10T12:22:19.039044Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.039295Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.039634Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.040012Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_redirection_404.ibd' OS error: 103
2025-06-10T12:22:19.040336Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.040633Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.041418Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_redirection_404`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.042157Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_redirection_404` because it could not be opened.
2025-06-10T12:22:19.042660Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.042912Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.043166Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.043630Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_redirection_groups.ibd' OS error: 103
2025-06-10T12:22:19.044013Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.044303Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.044810Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_redirection_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.045422Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_redirection_groups` because it could not be opened.
2025-06-10T12:22:19.046026Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.046286Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.046612Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.047143Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_redirection_items.ibd' OS error: 103
2025-06-10T12:22:19.047505Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.047797Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.048651Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_redirection_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.050154Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_redirection_items` because it could not be opened.
2025-06-10T12:22:19.051536Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.051832Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.052152Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.052712Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_redirection_logs.ibd' OS error: 103
2025-06-10T12:22:19.053084Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.053347Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.053798Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_redirection_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.054382Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_redirection_logs` because it could not be opened.
2025-06-10T12:22:19.054832Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.055102Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.055377Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.055833Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_revslider_css.ibd' OS error: 103
2025-06-10T12:22:19.056275Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.056541Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.057085Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_revslider_css`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.057710Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_revslider_css` because it could not be opened.
2025-06-10T12:22:19.058180Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.058457Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.058830Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.059272Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_revslider_css_bkp.ibd' OS error: 103
2025-06-10T12:22:19.059731Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.059997Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.060382Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_revslider_css_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.061086Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_revslider_css_bkp` because it could not be opened.
2025-06-10T12:22:19.061503Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.061885Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.062138Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.062613Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_revslider_layer_animations.ibd' OS error: 103
2025-06-10T12:22:19.063015Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.063261Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.063777Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_revslider_layer_animations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.064372Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_revslider_layer_animations` because it could not be opened.
2025-06-10T12:22:19.064874Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.065119Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.065375Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.065828Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_revslider_layer_animations_bkp.ibd' OS error: 103
2025-06-10T12:22:19.066176Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.066422Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.067022Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_revslider_layer_animations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.067673Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_revslider_layer_animations_bkp` because it could not be opened.
2025-06-10T12:22:19.068277Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.068768Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.069047Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.069417Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_revslider_navigations.ibd' OS error: 103
2025-06-10T12:22:19.069921Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.070172Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.070617Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_revslider_navigations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.071247Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_revslider_navigations` because it could not be opened.
2025-06-10T12:22:19.071706Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.072090Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.072394Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.072843Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_revslider_navigations_bkp.ibd' OS error: 103
2025-06-10T12:22:19.073188Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.073437Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.073966Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_revslider_navigations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.074682Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_revslider_navigations_bkp` because it could not be opened.
2025-06-10T12:22:19.075113Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.075377Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.075790Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.076178Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_revslider_sliders.ibd' OS error: 103
2025-06-10T12:22:19.076587Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.076897Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.077315Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_revslider_sliders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.078078Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_revslider_sliders` because it could not be opened.
2025-06-10T12:22:19.078475Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.078841Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.079103Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.079467Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_revslider_sliders_bkp.ibd' OS error: 103
2025-06-10T12:22:19.080043Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.080436Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.080984Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_revslider_sliders_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.081944Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_revslider_sliders_bkp` because it could not be opened.
2025-06-10T12:22:19.082632Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.082897Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.083227Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.083694Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_revslider_slides.ibd' OS error: 103
2025-06-10T12:22:19.084094Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.084384Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.084806Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_revslider_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.085442Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_revslider_slides` because it could not be opened.
2025-06-10T12:22:19.085879Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.086149Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.086459Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.086848Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_revslider_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:19.087215Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.087526Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.087946Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_revslider_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.088606Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_revslider_slides_bkp` because it could not be opened.
2025-06-10T12:22:19.089082Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.089447Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.089731Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.090149Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_revslider_static_slides.ibd' OS error: 103
2025-06-10T12:22:19.090689Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.091073Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.091662Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_revslider_static_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.092354Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_revslider_static_slides` because it could not be opened.
2025-06-10T12:22:19.092863Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.093113Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.093450Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.093889Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_revslider_static_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:19.094246Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.094616Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.095020Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_revslider_static_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.095737Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_revslider_static_slides_bkp` because it could not be opened.
2025-06-10T12:22:19.096150Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.096469Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.096725Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.097087Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_rich_web_icons.ibd' OS error: 103
2025-06-10T12:22:19.097544Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.097805Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.098191Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_rich_web_icons`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.098856Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_rich_web_icons` because it could not be opened.
2025-06-10T12:22:19.099221Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.099544Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.099797Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.100155Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_rich_web_timeline_manager.ibd' OS error: 103
2025-06-10T12:22:19.100579Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.100827Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.101212Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_rich_web_timeline_manager`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.102022Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_rich_web_timeline_manager` because it could not be opened.
2025-06-10T12:22:19.102460Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.102781Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.103144Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.103617Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_rich_web_timeline_options.ibd' OS error: 103
2025-06-10T12:22:19.103959Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.104205Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.104871Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_rich_web_timeline_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.105545Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_rich_web_timeline_options` because it could not be opened.
2025-06-10T12:22:19.106016Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.106293Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.106569Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.106951Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_rich_web_timeline_short_options.ibd' OS error: 103
2025-06-10T12:22:19.107371Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.107732Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.108182Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_rich_web_timeline_short_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.108895Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_rich_web_timeline_short_options` because it could not be opened.
2025-06-10T12:22:19.109463Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.109738Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.109997Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.110454Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_rich_web_timeline_style_options.ibd' OS error: 103
2025-06-10T12:22:19.110809Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.111054Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.111956Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_rich_web_timeline_style_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.113219Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_rich_web_timeline_style_options` because it could not be opened.
2025-06-10T12:22:19.113944Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.114390Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.114811Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.115420Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_rich_web_timeline_style_options_2.ibd' OS error: 103
2025-06-10T12:22:19.115913Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.116233Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.116651Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_rich_web_timeline_style_options_2`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.117343Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_rich_web_timeline_style_options_2` because it could not be opened.
2025-06-10T12:22:19.117835Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.118106Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.118458Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.118849Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_sbi_instagram_feed_locator.ibd' OS error: 103
2025-06-10T12:22:19.119318Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.119584Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.120003Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_sbi_instagram_feed_locator`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.120714Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_sbi_instagram_feed_locator` because it could not be opened.
2025-06-10T12:22:19.121274Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.121550Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.121826Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.122300Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_sbi_instagram_feeds_posts.ibd' OS error: 103
2025-06-10T12:22:19.122676Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.122932Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.123477Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_sbi_instagram_feeds_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.124098Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_sbi_instagram_feeds_posts` because it could not be opened.
2025-06-10T12:22:19.124604Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.124864Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.125127Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.125559Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_sbi_instagram_posts.ibd' OS error: 103
2025-06-10T12:22:19.125898Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.126162Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.126656Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_sbi_instagram_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.127270Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_sbi_instagram_posts` because it could not be opened.
2025-06-10T12:22:19.127675Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.128071Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.128502Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.128869Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:19.129325Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.129569Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.129961Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.130622Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:19.131141Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.131452Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.131716Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.132082Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:19.132580Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.132877Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.133344Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.134203Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:19.134694Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.134996Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.135364Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.135858Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:19.136247Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.136510Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.136902Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.137499Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_termmeta` because it could not be opened.
2025-06-10T12:22:19.137862Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.138125Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.138609Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.139032Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_terms.ibd' OS error: 103
2025-06-10T12:22:19.139499Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.139743Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.140159Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.141003Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_terms` because it could not be opened.
2025-06-10T12:22:19.141738Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.142101Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.142581Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.142946Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:19.143313Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.143575Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.143985Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.145414Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_usermeta` because it could not be opened.
2025-06-10T12:22:19.147176Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.147634Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.147936Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.148389Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_users.ibd' OS error: 103
2025-06-10T12:22:19.148746Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.149010Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.149439Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.150020Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_users` because it could not be opened.
2025-06-10T12:22:19.150420Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.150726Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.151078Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.151496Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_wc_admin_note_actions.ibd' OS error: 103
2025-06-10T12:22:19.151924Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.152184Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.152708Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_wc_admin_note_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.153404Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_wc_admin_note_actions` because it could not be opened.
2025-06-10T12:22:19.154048Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.154397Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.155118Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.155997Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_wc_admin_notes.ibd' OS error: 103
2025-06-10T12:22:19.156466Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.156813Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.157381Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_wc_admin_notes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.158115Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_wc_admin_notes` because it could not be opened.
2025-06-10T12:22:19.158545Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.158898Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.159159Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.159521Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_wc_category_lookup.ibd' OS error: 103
2025-06-10T12:22:19.159944Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.160193Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.160592Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_wc_category_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.161180Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_wc_category_lookup` because it could not be opened.
2025-06-10T12:22:19.161555Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.161894Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.162151Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.162514Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_wc_customer_lookup.ibd' OS error: 103
2025-06-10T12:22:19.162928Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.163175Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.163641Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_wc_customer_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.164258Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_wc_customer_lookup` because it could not be opened.
2025-06-10T12:22:19.164687Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.164957Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.165228Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.165627Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_wc_order_coupon_lookup.ibd' OS error: 103
2025-06-10T12:22:19.165985Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.166262Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.166688Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_wc_order_coupon_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.167293Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_wc_order_coupon_lookup` because it could not be opened.
2025-06-10T12:22:19.167737Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.168003Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.168289Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.168690Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_wc_order_product_lookup.ibd' OS error: 103
2025-06-10T12:22:19.169047Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.169307Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.169760Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_wc_order_product_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.170426Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_wc_order_product_lookup` because it could not be opened.
2025-06-10T12:22:19.170860Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.171121Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.171392Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.171822Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_wc_order_stats.ibd' OS error: 103
2025-06-10T12:22:19.172162Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.172422Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.172878Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_wc_order_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.173452Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_wc_order_stats` because it could not be opened.
2025-06-10T12:22:19.173848Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.174135Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.174405Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.174796Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_wc_order_tax_lookup.ibd' OS error: 103
2025-06-10T12:22:19.175146Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.175404Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.175858Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_wc_order_tax_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.176671Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_wc_order_tax_lookup` because it could not be opened.
2025-06-10T12:22:19.177090Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.177348Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.177690Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.178052Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_wc_product_meta_lookup.ibd' OS error: 103
2025-06-10T12:22:19.178388Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.178708Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.179101Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_wc_product_meta_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.179737Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_wc_product_meta_lookup` because it could not be opened.
2025-06-10T12:22:19.180121Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.180375Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.180704Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.181064Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_wc_reserved_stock.ibd' OS error: 103
2025-06-10T12:22:19.181390Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.181831Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.182268Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_wc_reserved_stock`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.182888Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_wc_reserved_stock` because it could not be opened.
2025-06-10T12:22:19.183361Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.183715Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.183977Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.184338Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_wc_tax_rate_classes.ibd' OS error: 103
2025-06-10T12:22:19.184770Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.185018Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.185416Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_wc_tax_rate_classes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.186103Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_wc_tax_rate_classes` because it could not be opened.
2025-06-10T12:22:19.186703Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.187021Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.187275Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.187753Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_wc_webhooks.ibd' OS error: 103
2025-06-10T12:22:19.188136Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.188520Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.189142Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_wc_webhooks`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.189806Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_wc_webhooks` because it could not be opened.
2025-06-10T12:22:19.190208Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.190471Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.190848Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.191217Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_woocommerce_api_keys.ibd' OS error: 103
2025-06-10T12:22:19.191630Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.191927Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.192427Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_woocommerce_api_keys`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.193411Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_woocommerce_api_keys` because it could not be opened.
2025-06-10T12:22:19.193918Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.194190Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.194531Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.195380Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_woocommerce_attribute_taxonomies.ibd' OS error: 103
2025-06-10T12:22:19.195909Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.196200Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.196594Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_woocommerce_attribute_taxonomies`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.197620Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_woocommerce_attribute_taxonomies` because it could not be opened.
2025-06-10T12:22:19.198254Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.198515Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.198774Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.199211Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_woocommerce_downloadable_product_permissions.ibd' OS error: 103
2025-06-10T12:22:19.199593Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.199881Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.200303Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_woocommerce_downloadable_product_permissions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.200961Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_woocommerce_downloadable_product_permissions` because it could not be opened.
2025-06-10T12:22:19.201546Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.201860Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.202281Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.202769Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_woocommerce_log.ibd' OS error: 103
2025-06-10T12:22:19.203223Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.203496Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.204029Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_woocommerce_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.204779Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_woocommerce_log` because it could not be opened.
2025-06-10T12:22:19.205470Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.205734Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.206120Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.206559Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_woocommerce_order_itemmeta.ibd' OS error: 103
2025-06-10T12:22:19.207202Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.207635Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.208168Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_woocommerce_order_itemmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.208729Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_woocommerce_order_itemmeta` because it could not be opened.
2025-06-10T12:22:19.209349Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.209596Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.209952Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.210431Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_woocommerce_order_items.ibd' OS error: 103
2025-06-10T12:22:19.210765Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.211111Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.211506Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_woocommerce_order_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.212372Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_woocommerce_order_items` because it could not be opened.
2025-06-10T12:22:19.212791Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.213128Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.213564Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.213989Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_woocommerce_payment_tokenmeta.ibd' OS error: 103
2025-06-10T12:22:19.214365Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.214627Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.215070Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_woocommerce_payment_tokenmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.215681Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_woocommerce_payment_tokenmeta` because it could not be opened.
2025-06-10T12:22:19.216154Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.216415Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.216683Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.217110Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_woocommerce_payment_tokens.ibd' OS error: 103
2025-06-10T12:22:19.217473Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.217732Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.218253Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_woocommerce_payment_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.218979Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_woocommerce_payment_tokens` because it could not be opened.
2025-06-10T12:22:19.219439Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.219707Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.220083Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.220508Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_woocommerce_sessions.ibd' OS error: 103
2025-06-10T12:22:19.220920Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.221190Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.221602Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_woocommerce_sessions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.222264Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_woocommerce_sessions` because it could not be opened.
2025-06-10T12:22:19.222683Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.223055Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.223399Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.224024Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_woocommerce_shipping_zone_locations.ibd' OS error: 103
2025-06-10T12:22:19.224534Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.224871Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.225285Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_woocommerce_shipping_zone_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.225983Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_woocommerce_shipping_zone_locations` because it could not be opened.
2025-06-10T12:22:19.226614Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.226994Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.227254Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.227614Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_woocommerce_shipping_zone_methods.ibd' OS error: 103
2025-06-10T12:22:19.228065Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.228538Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.229062Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_woocommerce_shipping_zone_methods`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.229678Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_woocommerce_shipping_zone_methods` because it could not be opened.
2025-06-10T12:22:19.230170Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.230434Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.230707Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.231122Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_woocommerce_shipping_zones.ibd' OS error: 103
2025-06-10T12:22:19.231490Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.231930Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.232386Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_woocommerce_shipping_zones`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.233158Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_woocommerce_shipping_zones` because it could not be opened.
2025-06-10T12:22:19.233680Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.234023Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.234298Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.234683Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_woocommerce_tax_rate_locations.ibd' OS error: 103
2025-06-10T12:22:19.235100Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.235365Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.235815Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_woocommerce_tax_rate_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.236459Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_woocommerce_tax_rate_locations` because it could not be opened.
2025-06-10T12:22:19.237001Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.237348Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.237602Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.238059Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_woocommerce_tax_rates.ibd' OS error: 103
2025-06-10T12:22:19.238391Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.238651Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.239135Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_woocommerce_tax_rates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.239751Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_woocommerce_tax_rates` because it could not be opened.
2025-06-10T12:22:19.240406Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.240676Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.241088Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.241457Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_wpgmza.ibd' OS error: 103
2025-06-10T12:22:19.241872Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.242170Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.242556Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_wpgmza`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.243210Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_wpgmza` because it could not be opened.
2025-06-10T12:22:19.243608Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.244069Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.244403Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.245009Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_wpgmza_circles.ibd' OS error: 103
2025-06-10T12:22:19.245671Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.246106Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.246748Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_wpgmza_circles`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.247575Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_wpgmza_circles` because it could not be opened.
2025-06-10T12:22:19.248259Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.248754Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.249131Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.249892Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_wpgmza_maps.ibd' OS error: 103
2025-06-10T12:22:19.250468Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.250980Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.251800Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_wpgmza_maps`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.253049Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_wpgmza_maps` because it could not be opened.
2025-06-10T12:22:19.253972Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.254602Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.255178Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.255920Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_wpgmza_polygon.ibd' OS error: 103
2025-06-10T12:22:19.256802Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.257380Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.258338Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_wpgmza_polygon`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.259973Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_wpgmza_polygon` because it could not be opened.
2025-06-10T12:22:19.261014Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.261771Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.262351Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.263052Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_wpgmza_polylines.ibd' OS error: 103
2025-06-10T12:22:19.263771Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.264326Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.265073Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_wpgmza_polylines`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.266271Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_wpgmza_polylines` because it could not be opened.
2025-06-10T12:22:19.266861Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.267228Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.267688Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.268366Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_wpgmza_rectangles.ibd' OS error: 103
2025-06-10T12:22:19.269064Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.269735Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.270708Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_wpgmza_rectangles`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.272385Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_wpgmza_rectangles` because it could not be opened.
2025-06-10T12:22:19.273812Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.274530Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.275563Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.276602Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:19.277247Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.277759Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.278663Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.279612Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:19.280760Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.281278Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.281763Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.282297Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:19.282872Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.283383Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.284151Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.286373Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:19.288189Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.288682Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.289103Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.289740Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:19.290512Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.291054Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.292229Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.293841Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:19.295199Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.296231Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.297190Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.298298Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem11\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:19.298931Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.299372Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.300118Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem11/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.301750Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem11/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:19.302895Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.303496Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.304280Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.305711Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_actionscheduler_actions.ibd' OS error: 103
2025-06-10T12:22:19.307592Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.308108Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.308868Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_actionscheduler_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.310168Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_actionscheduler_actions` because it could not be opened.
2025-06-10T12:22:19.311572Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.312924Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.313396Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.314274Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_actionscheduler_claims.ibd' OS error: 103
2025-06-10T12:22:19.315170Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.315980Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.316995Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_actionscheduler_claims`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.318412Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_actionscheduler_claims` because it could not be opened.
2025-06-10T12:22:19.319266Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.319780Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.320459Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.321382Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_actionscheduler_groups.ibd' OS error: 103
2025-06-10T12:22:19.322388Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.323041Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.324523Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_actionscheduler_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.327315Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_actionscheduler_groups` because it could not be opened.
2025-06-10T12:22:19.328395Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.328955Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.329590Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.330514Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_actionscheduler_logs.ibd' OS error: 103
2025-06-10T12:22:19.331366Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.331892Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.332887Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_actionscheduler_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.334260Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_actionscheduler_logs` because it could not be opened.
2025-06-10T12:22:19.335125Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.335548Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.336101Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.336889Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:19.337578Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.338010Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.339453Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.340311Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:19.341070Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.341965Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.342752Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.343674Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_comments.ibd' OS error: 103
2025-06-10T12:22:19.344473Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.345114Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.345661Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.346974Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_comments` because it could not be opened.
2025-06-10T12:22:19.347719Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.348148Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.348522Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.348890Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_csshero4.ibd' OS error: 103
2025-06-10T12:22:19.349341Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.349858Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.350375Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_csshero4`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.351147Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_csshero4` because it could not be opened.
2025-06-10T12:22:19.351714Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.352082Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.352505Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.353053Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:19.353438Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.353756Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.354320Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.355117Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_fbv` because it could not be opened.
2025-06-10T12:22:19.355674Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.356007Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.356369Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.357033Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:19.357822Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.358343Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.359085Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.359822Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:19.360398Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.360821Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.361081Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.361505Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_gg_attributes.ibd' OS error: 103
2025-06-10T12:22:19.361824Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.362072Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.362565Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_gg_attributes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.363121Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_gg_attributes` because it could not be opened.
2025-06-10T12:22:19.363580Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.363837Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.364364Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.364778Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_gg_cdn.ibd' OS error: 103
2025-06-10T12:22:19.365111Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.365463Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.366298Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_gg_cdn`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.367123Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_gg_cdn` because it could not be opened.
2025-06-10T12:22:19.367835Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.368237Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.368768Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.369720Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_gg_folders.ibd' OS error: 103
2025-06-10T12:22:19.371005Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.371277Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.371799Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_gg_folders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.372439Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_gg_folders` because it could not be opened.
2025-06-10T12:22:19.372915Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.373332Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.373667Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.374031Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_gg_galleries.ibd' OS error: 103
2025-06-10T12:22:19.374355Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.374752Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.375192Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_gg_galleries`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.375824Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_gg_galleries` because it could not be opened.
2025-06-10T12:22:19.376258Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.376600Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.376887Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.377317Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_gg_galleries_excluded.ibd' OS error: 103
2025-06-10T12:22:19.377828Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.378131Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.378652Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_gg_galleries_excluded`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.379223Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_gg_galleries_excluded` because it could not be opened.
2025-06-10T12:22:19.379767Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.380199Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.380576Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.380957Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_gg_galleries_resources.ibd' OS error: 103
2025-06-10T12:22:19.381310Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.381638Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.382034Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_gg_galleries_resources`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.382671Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_gg_galleries_resources` because it could not be opened.
2025-06-10T12:22:19.383080Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.383335Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.383659Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.384026Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_gg_image_optimize.ibd' OS error: 103
2025-06-10T12:22:19.384358Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.384669Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.385061Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_gg_image_optimize`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.385772Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_gg_image_optimize` because it could not be opened.
2025-06-10T12:22:19.386152Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.386483Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.386813Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.387206Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_gg_membership_presets.ibd' OS error: 103
2025-06-10T12:22:19.387624Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.387889Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.388288Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_gg_membership_presets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.389038Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_gg_membership_presets` because it could not be opened.
2025-06-10T12:22:19.389466Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.389771Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.390078Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.390528Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_gg_photos.ibd' OS error: 103
2025-06-10T12:22:19.390923Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.391171Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.391612Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_gg_photos`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.392155Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_gg_photos` because it could not be opened.
2025-06-10T12:22:19.392754Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.393085Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.393419Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.393812Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_gg_photos_pos.ibd' OS error: 103
2025-06-10T12:22:19.394139Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.394424Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.394913Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_gg_photos_pos`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.395559Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_gg_photos_pos` because it could not be opened.
2025-06-10T12:22:19.395989Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.396246Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.396560Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.397079Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_gg_photos_settings.ibd' OS error: 103
2025-06-10T12:22:19.397477Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.397825Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.398437Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_gg_photos_settings`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.399071Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_gg_photos_settings` because it could not be opened.
2025-06-10T12:22:19.399581Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.399832Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.400091Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.400563Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_gg_settings_presets.ibd' OS error: 103
2025-06-10T12:22:19.401677Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.402647Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.403733Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_gg_settings_presets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.404426Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_gg_settings_presets` because it could not be opened.
2025-06-10T12:22:19.404989Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.405297Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.405606Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.405997Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_gg_settings_sets.ibd' OS error: 103
2025-06-10T12:22:19.406392Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.406663Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.407078Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_gg_settings_sets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.407695Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_gg_settings_sets` because it could not be opened.
2025-06-10T12:22:19.408402Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.408708Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.408987Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.409421Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_gg_stats.ibd' OS error: 103
2025-06-10T12:22:19.409797Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.410063Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.410540Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_gg_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.411111Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_gg_stats` because it could not be opened.
2025-06-10T12:22:19.411556Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.411820Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.412091Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.412498Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_gg_tags.ibd' OS error: 103
2025-06-10T12:22:19.412822Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.413081Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.413518Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_gg_tags`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.414077Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_gg_tags` because it could not be opened.
2025-06-10T12:22:19.414580Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.414860Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.415125Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.415612Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_links.ibd' OS error: 103
2025-06-10T12:22:19.416055Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.416399Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.416808Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.417450Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_links` because it could not be opened.
2025-06-10T12:22:19.418132Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.418456Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.418727Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.419093Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_options.ibd' OS error: 103
2025-06-10T12:22:19.419497Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.419826Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.420234Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.420849Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_options` because it could not be opened.
2025-06-10T12:22:19.421353Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.421648Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.421916Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.422285Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_post_views.ibd' OS error: 103
2025-06-10T12:22:19.422714Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.422960Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.423404Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_post_views`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.423990Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_post_views` because it could not be opened.
2025-06-10T12:22:19.424470Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.424801Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.425068Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.425513Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:19.425847Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.426109Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.426698Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.427335Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_postmeta` because it could not be opened.
2025-06-10T12:22:19.427766Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.428043Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.428397Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.428779Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_posts.ibd' OS error: 103
2025-06-10T12:22:19.429155Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.429526Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.430025Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.430641Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_posts` because it could not be opened.
2025-06-10T12:22:19.431028Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.431416Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.431691Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.432166Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_redirection_404.ibd' OS error: 103
2025-06-10T12:22:19.432601Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.432885Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.433385Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_redirection_404`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.434481Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_redirection_404` because it could not be opened.
2025-06-10T12:22:19.434965Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.435304Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.435579Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.435972Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_redirection_groups.ibd' OS error: 103
2025-06-10T12:22:19.436429Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.436735Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.437217Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_redirection_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.437873Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_redirection_groups` because it could not be opened.
2025-06-10T12:22:19.438423Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.438756Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.439075Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.439657Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_redirection_items.ibd' OS error: 103
2025-06-10T12:22:19.440007Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.440382Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.440782Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_redirection_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.441449Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_redirection_items` because it could not be opened.
2025-06-10T12:22:19.441905Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.442222Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.442560Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.442926Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_redirection_logs.ibd' OS error: 103
2025-06-10T12:22:19.443329Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.443594Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.443990Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_redirection_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.444804Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_redirection_logs` because it could not be opened.
2025-06-10T12:22:19.445365Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.445633Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.446012Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.446442Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_revslider_css.ibd' OS error: 103
2025-06-10T12:22:19.446783Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.447048Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.447505Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_revslider_css`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.448072Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_revslider_css` because it could not be opened.
2025-06-10T12:22:19.448518Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.448767Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.449022Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.449463Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_revslider_css_bkp.ibd' OS error: 103
2025-06-10T12:22:19.449792Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.450037Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.450517Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_revslider_css_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.451062Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_revslider_css_bkp` because it could not be opened.
2025-06-10T12:22:19.451560Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.451882Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.452164Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.452540Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_revslider_layer_animations.ibd' OS error: 103
2025-06-10T12:22:19.452900Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.453241Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.453707Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_revslider_layer_animations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.454320Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_revslider_layer_animations` because it could not be opened.
2025-06-10T12:22:19.454753Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.455013Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.455359Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.455736Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_revslider_layer_animations_bkp.ibd' OS error: 103
2025-06-10T12:22:19.456169Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.456431Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.456836Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_revslider_layer_animations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.457498Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_revslider_layer_animations_bkp` because it could not be opened.
2025-06-10T12:22:19.457919Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.458257Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.458560Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.458933Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_revslider_navigations.ibd' OS error: 103
2025-06-10T12:22:19.459350Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.459612Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.460012Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_revslider_navigations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.460690Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_revslider_navigations` because it could not be opened.
2025-06-10T12:22:19.461222Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.461498Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.461957Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.462498Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_revslider_navigations_bkp.ibd' OS error: 103
2025-06-10T12:22:19.463028Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.463337Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.463749Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_revslider_navigations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.464886Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_revslider_navigations_bkp` because it could not be opened.
2025-06-10T12:22:19.466611Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.467340Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.467619Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.468058Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_revslider_sliders.ibd' OS error: 103
2025-06-10T12:22:19.468404Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.468687Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.469125Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_revslider_sliders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.469702Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_revslider_sliders` because it could not be opened.
2025-06-10T12:22:19.470243Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.470509Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.470817Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.471198Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_revslider_sliders_bkp.ibd' OS error: 103
2025-06-10T12:22:19.471555Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.471879Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.472462Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_revslider_sliders_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.473110Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_revslider_sliders_bkp` because it could not be opened.
2025-06-10T12:22:19.473572Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.474005Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.474352Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.474779Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_revslider_slides.ibd' OS error: 103
2025-06-10T12:22:19.475136Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.475465Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.475934Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_revslider_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.476511Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_revslider_slides` because it could not be opened.
2025-06-10T12:22:19.476978Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.477245Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.477585Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.478001Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_revslider_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:19.478353Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.478830Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.479248Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_revslider_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.479875Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_revslider_slides_bkp` because it could not be opened.
2025-06-10T12:22:19.480286Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.480538Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.480847Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.481256Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_revslider_static_slides.ibd' OS error: 103
2025-06-10T12:22:19.481597Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.481966Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.482394Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_revslider_static_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.483051Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_revslider_static_slides` because it could not be opened.
2025-06-10T12:22:19.483456Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.483732Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.484019Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.484377Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_revslider_static_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:19.484897Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.485260Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.485745Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_revslider_static_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.486387Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_revslider_static_slides_bkp` because it could not be opened.
2025-06-10T12:22:19.486880Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.487293Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.487556Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.487991Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_rich_web_icons.ibd' OS error: 103
2025-06-10T12:22:19.488315Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.488595Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.489075Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_rich_web_icons`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.489622Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_rich_web_icons` because it could not be opened.
2025-06-10T12:22:19.490127Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.490436Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.490727Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.491134Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_rich_web_timeline_manager.ibd' OS error: 103
2025-06-10T12:22:19.491741Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.492232Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.492960Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_rich_web_timeline_manager`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.493736Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_rich_web_timeline_manager` because it could not be opened.
2025-06-10T12:22:19.494243Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.494492Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.494786Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.495161Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_rich_web_timeline_options.ibd' OS error: 103
2025-06-10T12:22:19.495521Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.495806Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.496213Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_rich_web_timeline_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.497411Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_rich_web_timeline_options` because it could not be opened.
2025-06-10T12:22:19.498384Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.498658Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.499010Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.499391Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_rich_web_timeline_short_options.ibd' OS error: 103
2025-06-10T12:22:19.499788Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.500075Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.500489Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_rich_web_timeline_short_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.501126Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_rich_web_timeline_short_options` because it could not be opened.
2025-06-10T12:22:19.501584Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.501869Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.502144Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.502530Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_rich_web_timeline_style_options.ibd' OS error: 103
2025-06-10T12:22:19.502949Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.503210Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.503628Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_rich_web_timeline_style_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.504291Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_rich_web_timeline_style_options` because it could not be opened.
2025-06-10T12:22:19.504773Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.505071Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.505398Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.505828Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_rich_web_timeline_style_options_2.ibd' OS error: 103
2025-06-10T12:22:19.506395Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.506825Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.507357Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_rich_web_timeline_style_options_2`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.508045Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_rich_web_timeline_style_options_2` because it could not be opened.
2025-06-10T12:22:19.508495Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.508748Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.509127Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.509486Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_sbi_instagram_feed_locator.ibd' OS error: 103
2025-06-10T12:22:19.509875Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.510199Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.510633Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_sbi_instagram_feed_locator`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.511314Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_sbi_instagram_feed_locator` because it could not be opened.
2025-06-10T12:22:19.511716Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.512102Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.512356Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.512865Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_sbi_instagram_feeds_posts.ibd' OS error: 103
2025-06-10T12:22:19.513296Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.513544Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.514068Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_sbi_instagram_feeds_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.514747Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_sbi_instagram_feeds_posts` because it could not be opened.
2025-06-10T12:22:19.515254Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.515522Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.515849Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.516259Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_sbi_instagram_posts.ibd' OS error: 103
2025-06-10T12:22:19.516605Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.516941Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.517363Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_sbi_instagram_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.518025Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_sbi_instagram_posts` because it could not be opened.
2025-06-10T12:22:19.518421Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.518672Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.519039Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.519433Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:19.519767Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.520110Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.520499Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.521261Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:19.521677Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.522030Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.522295Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.522666Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:19.523162Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.523414Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.523860Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.524536Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:19.525021Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.525275Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.525537Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.526047Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:19.526359Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.526621Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.527144Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.527885Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_termmeta` because it could not be opened.
2025-06-10T12:22:19.528399Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.528926Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.529354Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.529937Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_terms.ibd' OS error: 103
2025-06-10T12:22:19.530260Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.530641Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.531136Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.532154Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_terms` because it could not be opened.
2025-06-10T12:22:19.532606Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.533110Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.533446Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.533828Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:19.534231Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.534497Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.534907Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.535538Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_usermeta` because it could not be opened.
2025-06-10T12:22:19.536037Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.536320Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.536589Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.537038Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_users.ibd' OS error: 103
2025-06-10T12:22:19.537371Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.537624Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.538170Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.538840Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_users` because it could not be opened.
2025-06-10T12:22:19.539375Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.539670Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.539926Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.540375Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_wc_admin_note_actions.ibd' OS error: 103
2025-06-10T12:22:19.540710Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.541021Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.541429Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_wc_admin_note_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.542080Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_wc_admin_note_actions` because it could not be opened.
2025-06-10T12:22:19.542533Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.542784Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.543174Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.543548Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_wc_admin_notes.ibd' OS error: 103
2025-06-10T12:22:19.543874Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.544202Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.544590Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_wc_admin_notes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.545227Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_wc_admin_notes` because it could not be opened.
2025-06-10T12:22:19.545732Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.546212Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.546475Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.546829Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_wc_category_lookup.ibd' OS error: 103
2025-06-10T12:22:19.547294Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.547538Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.547916Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_wc_category_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.548591Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_wc_category_lookup` because it could not be opened.
2025-06-10T12:22:19.549095Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.549470Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.549770Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.550333Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_wc_customer_lookup.ibd' OS error: 103
2025-06-10T12:22:19.550657Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.550900Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.551398Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_wc_customer_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.552040Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_wc_customer_lookup` because it could not be opened.
2025-06-10T12:22:19.552602Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.552878Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.553225Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.553593Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_wc_order_coupon_lookup.ibd' OS error: 103
2025-06-10T12:22:19.553983Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.554288Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.554685Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_wc_order_coupon_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.555387Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_wc_order_coupon_lookup` because it could not be opened.
2025-06-10T12:22:19.555860Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.556160Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.556436Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.556820Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_wc_order_product_lookup.ibd' OS error: 103
2025-06-10T12:22:19.557231Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.557490Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.557949Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_wc_order_product_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.558578Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_wc_order_product_lookup` because it could not be opened.
2025-06-10T12:22:19.559098Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.559370Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.559639Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.560104Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_wc_order_stats.ibd' OS error: 103
2025-06-10T12:22:19.560427Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.560675Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.561262Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_wc_order_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.561833Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_wc_order_stats` because it could not be opened.
2025-06-10T12:22:19.562267Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.562520Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.562776Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.563281Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_wc_order_tax_lookup.ibd' OS error: 103
2025-06-10T12:22:19.563620Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.563869Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.564352Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_wc_order_tax_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.565048Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_wc_order_tax_lookup` because it could not be opened.
2025-06-10T12:22:19.565479Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.565735Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.566091Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.566449Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_wc_product_meta_lookup.ibd' OS error: 103
2025-06-10T12:22:19.566847Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.567167Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.567557Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_wc_product_meta_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.568187Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_wc_product_meta_lookup` because it could not be opened.
2025-06-10T12:22:19.568573Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.568827Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.569157Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.569518Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_wc_reserved_stock.ibd' OS error: 103
2025-06-10T12:22:19.569844Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.570299Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.570714Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_wc_reserved_stock`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.571378Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_wc_reserved_stock` because it could not be opened.
2025-06-10T12:22:19.571786Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.572109Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.572548Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.573093Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_wc_tax_rate_classes.ibd' OS error: 103
2025-06-10T12:22:19.573532Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.573802Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.574313Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_wc_tax_rate_classes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.574920Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_wc_tax_rate_classes` because it could not be opened.
2025-06-10T12:22:19.575486Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.575747Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.576128Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.576640Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_wc_webhooks.ibd' OS error: 103
2025-06-10T12:22:19.577105Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.577411Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.577917Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_wc_webhooks`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.578655Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_wc_webhooks` because it could not be opened.
2025-06-10T12:22:19.579550Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.579855Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.580132Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.580566Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_woocommerce_api_keys.ibd' OS error: 103
2025-06-10T12:22:19.580924Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.581188Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.581635Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_woocommerce_api_keys`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.582230Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_woocommerce_api_keys` because it could not be opened.
2025-06-10T12:22:19.582692Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.582962Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.583236Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.583664Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_woocommerce_attribute_taxonomies.ibd' OS error: 103
2025-06-10T12:22:19.584053Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.584356Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.584835Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_woocommerce_attribute_taxonomies`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.585639Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_woocommerce_attribute_taxonomies` because it could not be opened.
2025-06-10T12:22:19.586405Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.586693Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.586957Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.587374Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_woocommerce_downloadable_product_permissions.ibd' OS error: 103
2025-06-10T12:22:19.587878Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.588150Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.588670Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_woocommerce_downloadable_product_permissions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.589374Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_woocommerce_downloadable_product_permissions` because it could not be opened.
2025-06-10T12:22:19.589926Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.590175Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.590645Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.591094Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_woocommerce_log.ibd' OS error: 103
2025-06-10T12:22:19.591574Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.592010Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.592628Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_woocommerce_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.593218Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_woocommerce_log` because it could not be opened.
2025-06-10T12:22:19.593684Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.593939Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.594196Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.594675Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_woocommerce_order_itemmeta.ibd' OS error: 103
2025-06-10T12:22:19.595022Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.595329Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.595743Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_woocommerce_order_itemmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.596398Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_woocommerce_order_itemmeta` because it could not be opened.
2025-06-10T12:22:19.596795Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.597044Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.597379Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.597821Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_woocommerce_order_items.ibd' OS error: 103
2025-06-10T12:22:19.598221Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.598527Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.598920Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_woocommerce_order_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.599581Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_woocommerce_order_items` because it could not be opened.
2025-06-10T12:22:19.599979Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.600245Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.600639Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.600994Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_woocommerce_payment_tokenmeta.ibd' OS error: 103
2025-06-10T12:22:19.601461Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.601729Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.602109Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_woocommerce_payment_tokenmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.602756Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_woocommerce_payment_tokenmeta` because it could not be opened.
2025-06-10T12:22:19.603161Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.603492Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.603746Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.604139Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_woocommerce_payment_tokens.ibd' OS error: 103
2025-06-10T12:22:19.604747Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.605079Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.605573Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_woocommerce_payment_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.606133Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_woocommerce_payment_tokens` because it could not be opened.
2025-06-10T12:22:19.606620Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.606926Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.607296Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.607812Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_woocommerce_sessions.ibd' OS error: 103
2025-06-10T12:22:19.608177Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.608535Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.609011Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_woocommerce_sessions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.609920Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_woocommerce_sessions` because it could not be opened.
2025-06-10T12:22:19.610598Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.610868Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.611170Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.611645Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_woocommerce_shipping_zone_locations.ibd' OS error: 103
2025-06-10T12:22:19.612084Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.612349Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.612824Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_woocommerce_shipping_zone_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.613420Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_woocommerce_shipping_zone_locations` because it could not be opened.
2025-06-10T12:22:19.613955Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.614208Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.614468Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.614956Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_woocommerce_shipping_zone_methods.ibd' OS error: 103
2025-06-10T12:22:19.615321Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.615706Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.616123Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_woocommerce_shipping_zone_methods`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.616845Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_woocommerce_shipping_zone_methods` because it could not be opened.
2025-06-10T12:22:19.617413Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.617982Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.618429Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.618878Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_woocommerce_shipping_zones.ibd' OS error: 103
2025-06-10T12:22:19.619227Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.619474Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.619955Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_woocommerce_shipping_zones`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.620564Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_woocommerce_shipping_zones` because it could not be opened.
2025-06-10T12:22:19.621068Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.621317Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.621645Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.622001Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_woocommerce_tax_rate_locations.ibd' OS error: 103
2025-06-10T12:22:19.622348Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.622715Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.623227Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_woocommerce_tax_rate_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.623980Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_woocommerce_tax_rate_locations` because it could not be opened.
2025-06-10T12:22:19.624447Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.624811Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.625062Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.625414Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_woocommerce_tax_rates.ibd' OS error: 103
2025-06-10T12:22:19.625846Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.626088Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.626472Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_woocommerce_tax_rates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.627281Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_woocommerce_tax_rates` because it could not be opened.
2025-06-10T12:22:19.627910Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.628199Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.628565Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.629089Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_wpgmza.ibd' OS error: 103
2025-06-10T12:22:19.629393Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.629791Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.630179Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_wpgmza`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.630809Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_wpgmza` because it could not be opened.
2025-06-10T12:22:19.631349Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.631698Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.631957Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.632318Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_wpgmza_circles.ibd' OS error: 103
2025-06-10T12:22:19.632750Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.632996Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.633543Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_wpgmza_circles`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.634107Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_wpgmza_circles` because it could not be opened.
2025-06-10T12:22:19.634527Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.634844Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.635097Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.635459Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_wpgmza_maps.ibd' OS error: 103
2025-06-10T12:22:19.635865Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.636107Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.636574Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_wpgmza_maps`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.637177Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_wpgmza_maps` because it could not be opened.
2025-06-10T12:22:19.637685Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.638052Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.638303Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.638873Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_wpgmza_polygon.ibd' OS error: 103
2025-06-10T12:22:19.639260Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.639573Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.640022Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_wpgmza_polygon`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.641648Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_wpgmza_polygon` because it could not be opened.
2025-06-10T12:22:19.642326Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.642723Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.642995Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.643543Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_wpgmza_polylines.ibd' OS error: 103
2025-06-10T12:22:19.643933Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.644297Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.644745Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_wpgmza_polylines`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.645416Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_wpgmza_polylines` because it could not be opened.
2025-06-10T12:22:19.645887Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.646202Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.646518Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.646972Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_wpgmza_rectangles.ibd' OS error: 103
2025-06-10T12:22:19.647447Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.647719Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.648223Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_wpgmza_rectangles`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.648811Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_wpgmza_rectangles` because it could not be opened.
2025-06-10T12:22:19.649351Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.649613Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.649912Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.650388Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:19.650826Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.651150Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.651561Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.652222Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:19.652763Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.653044Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.653359Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.653769Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:19.654157Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.654443Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.654827Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.655712Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:19.656226Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.656581Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.657056Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.657476Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:19.657840Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.658157Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.658613Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.659243Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:19.659662Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.659926Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.660212Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.660590Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem12\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:19.660952Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.661321Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.661771Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem12/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.662395Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem12/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:19.662852Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.663176Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.663447Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.663827Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_actionscheduler_actions.ibd' OS error: 103
2025-06-10T12:22:19.664260Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.664523Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.664930Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_actionscheduler_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.665598Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_actionscheduler_actions` because it could not be opened.
2025-06-10T12:22:19.666066Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.666335Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.666604Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.667064Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_actionscheduler_claims.ibd' OS error: 103
2025-06-10T12:22:19.667467Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.667724Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.668186Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_actionscheduler_claims`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.668980Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_actionscheduler_claims` because it could not be opened.
2025-06-10T12:22:19.669466Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.669737Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.670043Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.670433Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_actionscheduler_groups.ibd' OS error: 103
2025-06-10T12:22:19.670797Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.671088Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.671502Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_actionscheduler_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.672268Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_actionscheduler_groups` because it could not be opened.
2025-06-10T12:22:19.672884Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.673191Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.673463Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.674316Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_actionscheduler_logs.ibd' OS error: 103
2025-06-10T12:22:19.674722Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.675099Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.675558Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_actionscheduler_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.676305Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_actionscheduler_logs` because it could not be opened.
2025-06-10T12:22:19.676792Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.677066Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.677324Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.677686Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_cf7_vdata.ibd' OS error: 103
2025-06-10T12:22:19.678122Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.678386Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.678880Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_cf7_vdata`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.679454Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_cf7_vdata` because it could not be opened.
2025-06-10T12:22:19.679969Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.680233Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.680513Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.681088Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_cf7_vdata_entry.ibd' OS error: 103
2025-06-10T12:22:19.681489Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.681814Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.682277Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_cf7_vdata_entry`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.682961Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_cf7_vdata_entry` because it could not be opened.
2025-06-10T12:22:19.683367Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.683619Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.683992Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.684351Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:19.684659Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.684996Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.685375Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.686156Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:19.686565Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.686921Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.687192Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.687589Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_comments.ibd' OS error: 103
2025-06-10T12:22:19.688003Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.688264Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.688678Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.689294Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_comments` because it could not be opened.
2025-06-10T12:22:19.689665Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.690078Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.690339Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.690775Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_csshero4.ibd' OS error: 103
2025-06-10T12:22:19.691104Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.691353Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.691833Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_csshero4`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.692447Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_csshero4` because it could not be opened.
2025-06-10T12:22:19.692976Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.693319Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.693622Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.694154Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_db7_forms.ibd' OS error: 103
2025-06-10T12:22:19.694722Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.695013Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.695417Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_db7_forms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.696148Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_db7_forms` because it could not be opened.
2025-06-10T12:22:19.696734Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.697046Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.697481Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.697965Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:19.698343Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.698612Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.699064Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.699620Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_fbv` because it could not be opened.
2025-06-10T12:22:19.700066Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.700339Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.700616Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.701087Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:19.701610Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.701934Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.702336Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.702967Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:19.703447Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.703719Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.704182Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.705678Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_gg_attributes.ibd' OS error: 103
2025-06-10T12:22:19.706029Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.706341Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.706799Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_gg_attributes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.707394Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_gg_attributes` because it could not be opened.
2025-06-10T12:22:19.707837Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.708105Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.708394Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.708816Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_gg_cdn.ibd' OS error: 103
2025-06-10T12:22:19.709152Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.709421Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.709835Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_gg_cdn`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.710429Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_gg_cdn` because it could not be opened.
2025-06-10T12:22:19.710812Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.711080Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.711384Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.711772Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_gg_folders.ibd' OS error: 103
2025-06-10T12:22:19.712124Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.712420Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.712835Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_gg_folders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.713440Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_gg_folders` because it could not be opened.
2025-06-10T12:22:19.713885Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.714196Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.714804Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.715338Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_gg_galleries.ibd' OS error: 103
2025-06-10T12:22:19.715827Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.716106Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.716677Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_gg_galleries`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.717324Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_gg_galleries` because it could not be opened.
2025-06-10T12:22:19.717730Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.717984Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.718366Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.718730Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_gg_galleries_excluded.ibd' OS error: 103
2025-06-10T12:22:19.719068Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.719418Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.719804Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_gg_galleries_excluded`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.720462Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_gg_galleries_excluded` because it could not be opened.
2025-06-10T12:22:19.721218Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.721694Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.721971Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.722396Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_gg_galleries_resources.ibd' OS error: 103
2025-06-10T12:22:19.722742Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.722996Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.723486Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_gg_galleries_resources`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.724059Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_gg_galleries_resources` because it could not be opened.
2025-06-10T12:22:19.724551Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.724810Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.725068Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.725526Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_gg_image_optimize.ibd' OS error: 103
2025-06-10T12:22:19.725881Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.726289Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.726688Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_gg_image_optimize`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.727341Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_gg_image_optimize` because it could not be opened.
2025-06-10T12:22:19.727747Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.728000Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.728333Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.728749Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_gg_membership_presets.ibd' OS error: 103
2025-06-10T12:22:19.729134Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.729400Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.729804Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_gg_membership_presets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.730448Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_gg_membership_presets` because it could not be opened.
2025-06-10T12:22:19.730937Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.731300Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.731697Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.732117Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_gg_photos.ibd' OS error: 103
2025-06-10T12:22:19.732465Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.732727Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.733202Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_gg_photos`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.733777Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_gg_photos` because it could not be opened.
2025-06-10T12:22:19.734280Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.734563Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.734840Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.735420Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_gg_photos_pos.ibd' OS error: 103
2025-06-10T12:22:19.735772Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.736068Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.736493Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_gg_photos_pos`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.737040Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_gg_photos_pos` because it could not be opened.
2025-06-10T12:22:19.737548Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.737797Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.738129Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.738718Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_gg_photos_settings.ibd' OS error: 103
2025-06-10T12:22:19.739064Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.739829Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.740367Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_gg_photos_settings`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.741423Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_gg_photos_settings` because it could not be opened.
2025-06-10T12:22:19.741846Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.742119Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.742503Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.742870Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_gg_settings_presets.ibd' OS error: 103
2025-06-10T12:22:19.743203Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.743577Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.743992Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_gg_settings_presets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.744659Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_gg_settings_presets` because it could not be opened.
2025-06-10T12:22:19.745081Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.745473Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.745908Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.746597Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_gg_settings_sets.ibd' OS error: 103
2025-06-10T12:22:19.746992Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.747270Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.747768Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_gg_settings_sets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.748472Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_gg_settings_sets` because it could not be opened.
2025-06-10T12:22:19.749000Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.749298Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.749605Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.750016Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_gg_stats.ibd' OS error: 103
2025-06-10T12:22:19.750478Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.750748Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.751287Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_gg_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.751964Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_gg_stats` because it could not be opened.
2025-06-10T12:22:19.752493Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.752757Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.753016Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.753483Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_gg_tags.ibd' OS error: 103
2025-06-10T12:22:19.753804Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.754099Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.754596Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_gg_tags`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.755152Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_gg_tags` because it could not be opened.
2025-06-10T12:22:19.755658Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.755916Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.756178Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.756732Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_links.ibd' OS error: 103
2025-06-10T12:22:19.757066Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.757414Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.757818Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.758407Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_links` because it could not be opened.
2025-06-10T12:22:19.758769Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.759019Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.759354Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.759746Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_options.ibd' OS error: 103
2025-06-10T12:22:19.760052Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.760380Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.760840Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.761532Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_options` because it could not be opened.
2025-06-10T12:22:19.761979Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.762328Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.762860Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.763299Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_post_views.ibd' OS error: 103
2025-06-10T12:22:19.763824Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.764126Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.764602Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_post_views`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.765206Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_post_views` because it could not be opened.
2025-06-10T12:22:19.765747Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.766006Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.766338Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.766751Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:19.767065Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.767427Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.767830Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.768463Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_postmeta` because it could not be opened.
2025-06-10T12:22:19.769004Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.769968Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.770392Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.770911Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_posts.ibd' OS error: 103
2025-06-10T12:22:19.771402Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.771705Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.772207Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.772795Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_posts` because it could not be opened.
2025-06-10T12:22:19.773315Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.773572Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.773834Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.774318Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_redirection_404.ibd' OS error: 103
2025-06-10T12:22:19.774647Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.774897Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.775406Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_redirection_404`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.776002Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_redirection_404` because it could not be opened.
2025-06-10T12:22:19.776547Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.776806Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.777140Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.777540Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_redirection_groups.ibd' OS error: 103
2025-06-10T12:22:19.778214Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.778724Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.779375Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_redirection_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.779988Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_redirection_groups` because it could not be opened.
2025-06-10T12:22:19.780523Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.780773Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.781069Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.781500Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_redirection_items.ibd' OS error: 103
2025-06-10T12:22:19.781825Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.782149Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.782649Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_redirection_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.783236Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_redirection_items` because it could not be opened.
2025-06-10T12:22:19.783618Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.783886Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.784178Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.784557Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_redirection_logs.ibd' OS error: 103
2025-06-10T12:22:19.784937Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.785212Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.785613Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_redirection_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.786240Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_redirection_logs` because it could not be opened.
2025-06-10T12:22:19.786828Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.787119Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.787387Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.787763Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_revslider_css.ibd' OS error: 103
2025-06-10T12:22:19.788127Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.788387Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.788793Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_revslider_css`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.789383Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_revslider_css` because it could not be opened.
2025-06-10T12:22:19.789771Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.790063Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.790326Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.790706Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_revslider_css_bkp.ibd' OS error: 103
2025-06-10T12:22:19.791111Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.791356Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.791745Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_revslider_css_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.792351Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_revslider_css_bkp` because it could not be opened.
2025-06-10T12:22:19.792718Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.792974Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.793287Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.793647Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_revslider_layer_animations.ibd' OS error: 103
2025-06-10T12:22:19.794019Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.794354Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.794767Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_revslider_layer_animations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.795425Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_revslider_layer_animations` because it could not be opened.
2025-06-10T12:22:19.795855Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.796153Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.796407Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.796765Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_revslider_layer_animations_bkp.ibd' OS error: 103
2025-06-10T12:22:19.797342Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.797630Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.798234Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_revslider_layer_animations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.798942Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_revslider_layer_animations_bkp` because it could not be opened.
2025-06-10T12:22:19.799562Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.799814Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.800198Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.800767Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_revslider_navigations.ibd' OS error: 103
2025-06-10T12:22:19.801221Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.801511Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.801914Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_revslider_navigations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.802624Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_revslider_navigations` because it could not be opened.
2025-06-10T12:22:19.803108Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.803511Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.803784Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.804237Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_revslider_navigations_bkp.ibd' OS error: 103
2025-06-10T12:22:19.804577Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.804823Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.805292Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_revslider_navigations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.805844Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_revslider_navigations_bkp` because it could not be opened.
2025-06-10T12:22:19.806340Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.806589Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.806841Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.807290Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_revslider_sliders.ibd' OS error: 103
2025-06-10T12:22:19.807633Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.807886Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.808352Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_revslider_sliders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.808935Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_revslider_sliders` because it could not be opened.
2025-06-10T12:22:19.809404Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.809675Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.809977Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.810416Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_revslider_sliders_bkp.ibd' OS error: 103
2025-06-10T12:22:19.810779Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.811101Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.811521Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_revslider_sliders_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.812309Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_revslider_sliders_bkp` because it could not be opened.
2025-06-10T12:22:19.813127Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.813510Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.813908Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.814588Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_revslider_slides.ibd' OS error: 103
2025-06-10T12:22:19.815176Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.815550Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.816308Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_revslider_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.818349Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_revslider_slides` because it could not be opened.
2025-06-10T12:22:19.819001Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.819286Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.819563Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.820018Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_revslider_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:19.820373Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.820702Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.821316Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_revslider_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.822270Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_revslider_slides_bkp` because it could not be opened.
2025-06-10T12:22:19.823003Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.823387Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.823870Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.824434Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_revslider_static_slides.ibd' OS error: 103
2025-06-10T12:22:19.825051Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.825447Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.826140Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_revslider_static_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.827044Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_revslider_static_slides` because it could not be opened.
2025-06-10T12:22:19.827510Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.827868Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.828146Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.828528Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_revslider_static_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:19.829006Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.829265Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.829741Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_revslider_static_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.830346Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_revslider_static_slides_bkp` because it could not be opened.
2025-06-10T12:22:19.830821Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.831089Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.831358Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.831793Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_rich_web_icons.ibd' OS error: 103
2025-06-10T12:22:19.832137Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.832397Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.832850Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_rich_web_icons`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.833424Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_rich_web_icons` because it could not be opened.
2025-06-10T12:22:19.833858Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.834122Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.834390Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.834808Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_rich_web_timeline_manager.ibd' OS error: 103
2025-06-10T12:22:19.835174Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.835435Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.835902Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_rich_web_timeline_manager`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.836500Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_rich_web_timeline_manager` because it could not be opened.
2025-06-10T12:22:19.836959Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.837222Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.837491Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.837927Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_rich_web_timeline_options.ibd' OS error: 103
2025-06-10T12:22:19.838290Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.838601Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.839027Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_rich_web_timeline_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.839685Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_rich_web_timeline_options` because it could not be opened.
2025-06-10T12:22:19.840087Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.840352Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.840690Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.841066Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_rich_web_timeline_short_options.ibd' OS error: 103
2025-06-10T12:22:19.841443Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.841776Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.842195Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_rich_web_timeline_short_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.842886Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_rich_web_timeline_short_options` because it could not be opened.
2025-06-10T12:22:19.843347Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.843665Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.843931Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.844311Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_rich_web_timeline_style_options.ibd' OS error: 103
2025-06-10T12:22:19.844777Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.845227Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.845897Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_rich_web_timeline_style_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.846650Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_rich_web_timeline_style_options` because it could not be opened.
2025-06-10T12:22:19.847203Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.847460Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.847808Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.848167Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_rich_web_timeline_style_options_2.ibd' OS error: 103
2025-06-10T12:22:19.848632Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.848940Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.849442Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_rich_web_timeline_style_options_2`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.850362Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_rich_web_timeline_style_options_2` because it could not be opened.
2025-06-10T12:22:19.850952Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.851217Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.851595Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.851968Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_sbi_instagram_feed_locator.ibd' OS error: 103
2025-06-10T12:22:19.852351Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.852844Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.853263Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_sbi_instagram_feed_locator`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.853916Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_sbi_instagram_feed_locator` because it could not be opened.
2025-06-10T12:22:19.854368Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.854682Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.854951Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.855331Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_sbi_instagram_feeds_posts.ibd' OS error: 103
2025-06-10T12:22:19.855829Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.856098Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.856596Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_sbi_instagram_feeds_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.857226Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_sbi_instagram_feeds_posts` because it could not be opened.
2025-06-10T12:22:19.857964Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.858259Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.858593Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.858974Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_sbi_instagram_posts.ibd' OS error: 103
2025-06-10T12:22:19.859327Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.859645Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.860057Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_sbi_instagram_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.860709Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_sbi_instagram_posts` because it could not be opened.
2025-06-10T12:22:19.861547Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.861840Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.862106Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.862510Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_sgpb_subscribers.ibd' OS error: 103
2025-06-10T12:22:19.862883Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.863136Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.863585Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_sgpb_subscribers`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.864190Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_sgpb_subscribers` because it could not be opened.
2025-06-10T12:22:19.864667Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.865007Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.865430Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.865953Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_sgpb_subscription_error_log.ibd' OS error: 103
2025-06-10T12:22:19.866306Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.866637Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.867029Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_sgpb_subscription_error_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.867690Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_sgpb_subscription_error_log` because it could not be opened.
2025-06-10T12:22:19.868093Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.868345Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.868700Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.869059Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:19.869384Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.869710Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.870094Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.870780Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:19.871558Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.871868Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.872131Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.872588Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:19.872984Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.873257Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.873840Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.874399Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:19.874902Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.875153Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.875416Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.875937Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:19.876298Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.876704Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.877145Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.877822Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_termmeta` because it could not be opened.
2025-06-10T12:22:19.878540Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.878861Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.879132Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.879573Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_terms.ibd' OS error: 103
2025-06-10T12:22:19.880034Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.880283Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.881313Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.882635Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_terms` because it could not be opened.
2025-06-10T12:22:19.883068Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.883366Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.883701Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.884095Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:19.884411Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.884735Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.885132Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.885779Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_usermeta` because it could not be opened.
2025-06-10T12:22:19.886166Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.886420Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.886920Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.887320Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_users.ibd' OS error: 103
2025-06-10T12:22:19.887745Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.888014Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.888466Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.889086Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_users` because it could not be opened.
2025-06-10T12:22:19.889703Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.890055Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.890320Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.890794Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_wc_admin_note_actions.ibd' OS error: 103
2025-06-10T12:22:19.891150Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.891411Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.891872Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_wc_admin_note_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.892491Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_wc_admin_note_actions` because it could not be opened.
2025-06-10T12:22:19.892949Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.893201Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.893555Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.894014Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_wc_admin_notes.ibd' OS error: 103
2025-06-10T12:22:19.894354Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.894717Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.895128Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_wc_admin_notes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.895779Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_wc_admin_notes` because it could not be opened.
2025-06-10T12:22:19.896199Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.896539Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.896880Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.897327Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_wc_category_lookup.ibd' OS error: 103
2025-06-10T12:22:19.897788Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.898059Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.898585Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_wc_category_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.899186Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_wc_category_lookup` because it could not be opened.
2025-06-10T12:22:19.899633Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.899903Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.900329Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.900817Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_wc_customer_lookup.ibd' OS error: 103
2025-06-10T12:22:19.901309Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.901742Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.902153Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_wc_customer_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.902783Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_wc_customer_lookup` because it could not be opened.
2025-06-10T12:22:19.903590Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.903854Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.904114Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.904616Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_wc_download_log.ibd' OS error: 103
2025-06-10T12:22:19.904978Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.905228Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.905699Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_wc_download_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.906254Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_wc_download_log` because it could not be opened.
2025-06-10T12:22:19.906823Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.907078Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.907333Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.907785Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_wc_order_coupon_lookup.ibd' OS error: 103
2025-06-10T12:22:19.908132Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.908447Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.908866Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_wc_order_coupon_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.909624Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_wc_order_coupon_lookup` because it could not be opened.
2025-06-10T12:22:19.910042Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.910295Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.910626Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.910989Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_wc_order_product_lookup.ibd' OS error: 103
2025-06-10T12:22:19.911618Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.912506Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.913613Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_wc_order_product_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.914828Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_wc_order_product_lookup` because it could not be opened.
2025-06-10T12:22:19.915364Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.915628Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.916033Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.916388Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_wc_order_stats.ibd' OS error: 103
2025-06-10T12:22:19.916848Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.917110Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.917503Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_wc_order_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.918154Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_wc_order_stats` because it could not be opened.
2025-06-10T12:22:19.918594Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.918946Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.919207Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.919765Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_wc_order_tax_lookup.ibd' OS error: 103
2025-06-10T12:22:19.920204Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.920493Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.921020Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_wc_order_tax_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.921655Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_wc_order_tax_lookup` because it could not be opened.
2025-06-10T12:22:19.922188Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.922444Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.922702Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.923228Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_wc_product_meta_lookup.ibd' OS error: 103
2025-06-10T12:22:19.923569Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.923915Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.924302Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_wc_product_meta_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.924920Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_wc_product_meta_lookup` because it could not be opened.
2025-06-10T12:22:19.925314Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.925564Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.925916Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.926281Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_wc_reserved_stock.ibd' OS error: 103
2025-06-10T12:22:19.926617Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.926957Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.927349Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_wc_reserved_stock`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.928023Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_wc_reserved_stock` because it could not be opened.
2025-06-10T12:22:19.928390Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.928637Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.929006Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.929386Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_wc_tax_rate_classes.ibd' OS error: 103
2025-06-10T12:22:19.929769Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.930053Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.930464Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_wc_tax_rate_classes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.931082Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_wc_tax_rate_classes` because it could not be opened.
2025-06-10T12:22:19.931480Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.931774Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.932045Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.932425Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_wc_webhooks.ibd' OS error: 103
2025-06-10T12:22:19.932782Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.933044Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.933459Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_wc_webhooks`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.934191Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_wc_webhooks` because it could not be opened.
2025-06-10T12:22:19.934593Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.934882Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.935162Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.935546Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_woocommerce_api_keys.ibd' OS error: 103
2025-06-10T12:22:19.935949Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.936208Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.936622Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_woocommerce_api_keys`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.937240Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_woocommerce_api_keys` because it could not be opened.
2025-06-10T12:22:19.937618Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.937953Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.938213Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.938570Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_woocommerce_attribute_taxonomies.ibd' OS error: 103
2025-06-10T12:22:19.938994Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.939242Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.939664Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_woocommerce_attribute_taxonomies`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.940408Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_woocommerce_attribute_taxonomies` because it could not be opened.
2025-06-10T12:22:19.941141Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.941452Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.941806Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.942193Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_woocommerce_downloadable_product_permissions.ibd' OS error: 103
2025-06-10T12:22:19.942598Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.942943Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.943335Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_woocommerce_downloadable_product_permissions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.944243Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_woocommerce_downloadable_product_permissions` because it could not be opened.
2025-06-10T12:22:19.944829Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.945102Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.945442Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.945821Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_woocommerce_log.ibd' OS error: 103
2025-06-10T12:22:19.946624Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.946954Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.947414Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_woocommerce_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.948233Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_woocommerce_log` because it could not be opened.
2025-06-10T12:22:19.948727Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.949018Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.949295Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.949687Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_woocommerce_order_itemmeta.ibd' OS error: 103
2025-06-10T12:22:19.950108Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.950374Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.950795Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_woocommerce_order_itemmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.951455Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_woocommerce_order_itemmeta` because it could not be opened.
2025-06-10T12:22:19.951987Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.952305Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.952577Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.953012Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_woocommerce_order_items.ibd' OS error: 103
2025-06-10T12:22:19.953399Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.953669Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.954174Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_woocommerce_order_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.954810Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_woocommerce_order_items` because it could not be opened.
2025-06-10T12:22:19.955299Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.955553Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.955814Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.956248Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_woocommerce_payment_tokenmeta.ibd' OS error: 103
2025-06-10T12:22:19.956671Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.957073Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.957462Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_woocommerce_payment_tokenmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.958174Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_woocommerce_payment_tokenmeta` because it could not be opened.
2025-06-10T12:22:19.958590Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.958840Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.959216Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.959573Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_woocommerce_payment_tokens.ibd' OS error: 103
2025-06-10T12:22:19.959989Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.960277Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.960689Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_woocommerce_payment_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.961380Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_woocommerce_payment_tokens` because it could not be opened.
2025-06-10T12:22:19.961768Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.962153Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.962462Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.962842Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_woocommerce_sessions.ibd' OS error: 103
2025-06-10T12:22:19.963344Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.963643Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.964176Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_woocommerce_sessions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.964751Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_woocommerce_sessions` because it could not be opened.
2025-06-10T12:22:19.965231Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.965489Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.965749Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.966177Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_woocommerce_shipping_zone_locations.ibd' OS error: 103
2025-06-10T12:22:19.966545Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.966918Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.967462Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_woocommerce_shipping_zone_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.968203Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_woocommerce_shipping_zone_locations` because it could not be opened.
2025-06-10T12:22:19.968665Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.969012Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.969271Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.969636Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_woocommerce_shipping_zone_methods.ibd' OS error: 103
2025-06-10T12:22:19.970111Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.970374Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.970765Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_woocommerce_shipping_zone_methods`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.971432Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_woocommerce_shipping_zone_methods` because it could not be opened.
2025-06-10T12:22:19.971932Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.972208Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.972472Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.973021Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_woocommerce_shipping_zones.ibd' OS error: 103
2025-06-10T12:22:19.973420Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.974107Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.974547Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_woocommerce_shipping_zones`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.975201Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_woocommerce_shipping_zones` because it could not be opened.
2025-06-10T12:22:19.975654Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.976139Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.976551Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.977103Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_woocommerce_tax_rate_locations.ibd' OS error: 103
2025-06-10T12:22:19.978541Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.978827Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.979282Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_woocommerce_tax_rate_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.979953Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_woocommerce_tax_rate_locations` because it could not be opened.
2025-06-10T12:22:19.980437Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.980705Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.981015Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.981400Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_woocommerce_tax_rates.ibd' OS error: 103
2025-06-10T12:22:19.982021Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.982343Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.982757Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_woocommerce_tax_rates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.983799Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_woocommerce_tax_rates` because it could not be opened.
2025-06-10T12:22:19.984415Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.984697Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.985034Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.985412Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_wpgmza.ibd' OS error: 103
2025-06-10T12:22:19.985725Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.986136Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.986617Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_wpgmza`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.987249Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_wpgmza` because it could not be opened.
2025-06-10T12:22:19.987660Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.987995Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.988326Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.988778Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_wpgmza_circles.ibd' OS error: 103
2025-06-10T12:22:19.989198Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.989455Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.989981Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_wpgmza_circles`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.990546Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_wpgmza_circles` because it could not be opened.
2025-06-10T12:22:19.991019Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.991268Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.991541Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.992046Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_wpgmza_maps.ibd' OS error: 103
2025-06-10T12:22:19.992373Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.992625Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.993127Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_wpgmza_maps`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.993662Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_wpgmza_maps` because it could not be opened.
2025-06-10T12:22:19.994124Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.994372Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.994627Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.995135Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_wpgmza_polygon.ibd' OS error: 103
2025-06-10T12:22:19.995513Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.995780Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.996223Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_wpgmza_polygon`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.996816Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_wpgmza_polygon` because it could not be opened.
2025-06-10T12:22:19.997245Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:19.997540Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:19.997823Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:19.998220Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_wpgmza_polylines.ibd' OS error: 103
2025-06-10T12:22:19.998572Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:19.998877Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:19.999301Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_wpgmza_polylines`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:19.999920Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_wpgmza_polylines` because it could not be opened.
2025-06-10T12:22:20.000347Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.000613Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.000926Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.001312Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_wpgmza_rectangles.ibd' OS error: 103
2025-06-10T12:22:20.001660Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.001955Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.002391Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_wpgmza_rectangles`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.003002Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_wpgmza_rectangles` because it could not be opened.
2025-06-10T12:22:20.003887Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.004179Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.004444Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.004933Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_wpie_template.ibd' OS error: 103
2025-06-10T12:22:20.005313Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.005609Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.006075Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_wpie_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.006622Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_wpie_template` because it could not be opened.
2025-06-10T12:22:20.007165Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.007433Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.007708Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.008424Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_wpmailsmtp_debug_events.ibd' OS error: 103
2025-06-10T12:22:20.008789Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.009593Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.010226Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_wpmailsmtp_debug_events`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.010900Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_wpmailsmtp_debug_events` because it could not be opened.
2025-06-10T12:22:20.011465Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.011752Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.012027Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.012407Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_wpmailsmtp_tasks_meta.ibd' OS error: 103
2025-06-10T12:22:20.012829Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.013094Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.013506Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_wpmailsmtp_tasks_meta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.014154Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_wpmailsmtp_tasks_meta` because it could not be opened.
2025-06-10T12:22:20.014981Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.015291Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.015653Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.016110Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_wpmm_subscribers.ibd' OS error: 103
2025-06-10T12:22:20.016546Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.016938Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.017461Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_wpmm_subscribers`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.018196Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_wpmm_subscribers` because it could not be opened.
2025-06-10T12:22:20.018651Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.018995Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.019254Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.019616Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:20.020049Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.020298Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.020763Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.021338Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:20.022120Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.022449Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.022794Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.023158Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:20.023475Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.023848Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.024957Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.025539Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:20.025982Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.026257Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.026529Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.026941Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:20.027274Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.027537Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.027980Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.028737Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:20.029144Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.029418Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.029860Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.030256Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem13\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:20.030606Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.030931Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.031378Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem13/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.031996Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem13/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:20.032686Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.032956Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.033226Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.033609Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:20.033975Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.034241Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.034689Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.035332Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:20.035788Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.036042Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.036305Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.036784Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_comments.ibd' OS error: 103
2025-06-10T12:22:20.037124Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.037372Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.037831Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.038370Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_comments` because it could not be opened.
2025-06-10T12:22:20.038813Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.039067Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.039325Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.039834Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:20.040140Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.040505Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.041459Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.042280Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_fbv` because it could not be opened.
2025-06-10T12:22:20.042992Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.043300Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.043624Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.044067Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:20.044464Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.044750Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.045209Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.045869Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:20.046296Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.046549Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.046927Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.047368Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_gg_attributes.ibd' OS error: 103
2025-06-10T12:22:20.047741Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.048011Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.048604Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_gg_attributes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.049247Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_gg_attributes` because it could not be opened.
2025-06-10T12:22:20.049743Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.050026Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.050329Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.050731Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_gg_cdn.ibd' OS error: 103
2025-06-10T12:22:20.051056Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.051318Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.051755Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_gg_cdn`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.052310Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_gg_cdn` because it could not be opened.
2025-06-10T12:22:20.052713Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.052982Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.053253Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.053634Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_gg_folders.ibd' OS error: 103
2025-06-10T12:22:20.053995Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.054256Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.054696Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_gg_folders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.055482Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_gg_folders` because it could not be opened.
2025-06-10T12:22:20.055908Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.056178Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.056447Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.056911Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_gg_galleries.ibd' OS error: 103
2025-06-10T12:22:20.057249Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.057508Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.058006Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_gg_galleries`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.058571Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_gg_galleries` because it could not be opened.
2025-06-10T12:22:20.059009Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.059272Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.059543Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.059978Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_gg_galleries_excluded.ibd' OS error: 103
2025-06-10T12:22:20.060327Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.060584Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.061190Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_gg_galleries_excluded`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.061801Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_gg_galleries_excluded` because it could not be opened.
2025-06-10T12:22:20.062212Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.062460Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.062862Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.063222Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_gg_galleries_resources.ibd' OS error: 103
2025-06-10T12:22:20.063558Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.063898Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.064284Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_gg_galleries_resources`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.064974Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_gg_galleries_resources` because it could not be opened.
2025-06-10T12:22:20.065363Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.065689Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.065992Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.066435Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_gg_image_optimize.ibd' OS error: 103
2025-06-10T12:22:20.066861Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.067123Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.067556Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_gg_image_optimize`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.068179Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_gg_image_optimize` because it could not be opened.
2025-06-10T12:22:20.068723Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.069008Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.069364Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.069792Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_gg_membership_presets.ibd' OS error: 103
2025-06-10T12:22:20.070151Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.070418Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.070913Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_gg_membership_presets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.071474Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_gg_membership_presets` because it could not be opened.
2025-06-10T12:22:20.072178Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.072446Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.072817Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.073270Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_gg_photos.ibd' OS error: 103
2025-06-10T12:22:20.073585Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.074367Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.075050Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_gg_photos`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.075661Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_gg_photos` because it could not be opened.
2025-06-10T12:22:20.076146Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.076476Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.076775Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.077204Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_gg_photos_pos.ibd' OS error: 103
2025-06-10T12:22:20.077516Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.077757Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.078345Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_gg_photos_pos`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.079005Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_gg_photos_pos` because it could not be opened.
2025-06-10T12:22:20.079470Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.079732Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.080165Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.080539Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_gg_photos_settings.ibd' OS error: 103
2025-06-10T12:22:20.081205Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.081483Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.081989Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_gg_photos_settings`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.082661Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_gg_photos_settings` because it could not be opened.
2025-06-10T12:22:20.083377Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.083652Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.084026Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.084406Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_gg_settings_presets.ibd' OS error: 103
2025-06-10T12:22:20.084728Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.085105Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.085587Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_gg_settings_presets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.086327Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_gg_settings_presets` because it could not be opened.
2025-06-10T12:22:20.086705Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.087116Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.087373Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.087949Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_gg_settings_sets.ibd' OS error: 103
2025-06-10T12:22:20.088310Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.088600Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.089072Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_gg_settings_sets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.089664Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_gg_settings_sets` because it could not be opened.
2025-06-10T12:22:20.090117Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.090368Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.090621Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.091065Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_gg_stats.ibd' OS error: 103
2025-06-10T12:22:20.091378Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.091630Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.092123Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_gg_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.092716Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_gg_stats` because it could not be opened.
2025-06-10T12:22:20.093190Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.093442Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.093703Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.094214Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_gg_tags.ibd' OS error: 103
2025-06-10T12:22:20.094519Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.094762Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.095398Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_gg_tags`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.096060Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_gg_tags` because it could not be opened.
2025-06-10T12:22:20.096410Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.096656Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.097072Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.097430Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_links.ibd' OS error: 103
2025-06-10T12:22:20.097727Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.098124Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.098505Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.099284Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_links` because it could not be opened.
2025-06-10T12:22:20.099630Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.099978Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.100327Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.100691Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_newsletter.ibd' OS error: 103
2025-06-10T12:22:20.101124Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.101370Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.101971Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_newsletter`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.102508Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_newsletter` because it could not be opened.
2025-06-10T12:22:20.102985Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.103235Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.103489Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.103923Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_newsletter_emails.ibd' OS error: 103
2025-06-10T12:22:20.104249Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.104492Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.104980Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_newsletter_emails`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.105771Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_newsletter_emails` because it could not be opened.
2025-06-10T12:22:20.106221Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.106481Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.106737Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.107206Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_newsletter_sent.ibd' OS error: 103
2025-06-10T12:22:20.107528Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.107814Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.108272Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_newsletter_sent`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.108878Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_newsletter_sent` because it could not be opened.
2025-06-10T12:22:20.109460Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.109733Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.110118Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.110480Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_newsletter_stats.ibd' OS error: 103
2025-06-10T12:22:20.110876Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.111271Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.111657Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_newsletter_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.112378Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_newsletter_stats` because it could not be opened.
2025-06-10T12:22:20.112971Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.113238Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.113494Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.113981Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_newsletter_user_logs.ibd' OS error: 103
2025-06-10T12:22:20.114328Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.114576Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.115118Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_newsletter_user_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.115792Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_newsletter_user_logs` because it could not be opened.
2025-06-10T12:22:20.116243Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.116516Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.116835Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.117328Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_options.ibd' OS error: 103
2025-06-10T12:22:20.117708Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.118002Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.118415Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.119000Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_options` because it could not be opened.
2025-06-10T12:22:20.119399Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.119860Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.121184Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.121711Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_post_views.ibd' OS error: 103
2025-06-10T12:22:20.122459Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.122836Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.123374Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_post_views`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.123977Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_post_views` because it could not be opened.
2025-06-10T12:22:20.124428Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.124728Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.125004Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.125383Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:20.125754Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.126015Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.126422Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.127022Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_postmeta` because it could not be opened.
2025-06-10T12:22:20.127637Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.127999Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.128264Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.128635Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_posts.ibd' OS error: 103
2025-06-10T12:22:20.129040Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.129314Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.129780Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.130402Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_posts` because it could not be opened.
2025-06-10T12:22:20.130880Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.131132Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.131389Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.131818Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_revslider_css.ibd' OS error: 103
2025-06-10T12:22:20.132138Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.132386Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.132855Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_revslider_css`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.133443Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_revslider_css` because it could not be opened.
2025-06-10T12:22:20.133914Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.134182Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.134486Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.134945Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_revslider_css_bkp.ibd' OS error: 103
2025-06-10T12:22:20.135314Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.135572Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.136061Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_revslider_css_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.136623Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_revslider_css_bkp` because it could not be opened.
2025-06-10T12:22:20.137113Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.137370Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.137632Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.138057Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_revslider_layer_animations.ibd' OS error: 103
2025-06-10T12:22:20.138439Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.138764Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.139245Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_revslider_layer_animations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.139921Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_revslider_layer_animations` because it could not be opened.
2025-06-10T12:22:20.140326Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.140630Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.140910Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.141301Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_revslider_layer_animations_bkp.ibd' OS error: 103
2025-06-10T12:22:20.141709Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.141974Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.142384Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_revslider_layer_animations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.143031Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_revslider_layer_animations_bkp` because it could not be opened.
2025-06-10T12:22:20.143455Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.143745Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.144018Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.144396Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_revslider_navigations.ibd' OS error: 103
2025-06-10T12:22:20.144782Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.145046Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.145460Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_revslider_navigations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.146081Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_revslider_navigations` because it could not be opened.
2025-06-10T12:22:20.146700Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.147064Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.147418Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.147828Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_revslider_navigations_bkp.ibd' OS error: 103
2025-06-10T12:22:20.148260Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.148515Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.148924Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_revslider_navigations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.149705Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_revslider_navigations_bkp` because it could not be opened.
2025-06-10T12:22:20.150329Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.150708Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.151044Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.151472Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_revslider_sliders.ibd' OS error: 103
2025-06-10T12:22:20.151949Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.152218Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.152827Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_revslider_sliders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.153534Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_revslider_sliders` because it could not be opened.
2025-06-10T12:22:20.154040Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.154410Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.154782Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.155207Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_revslider_sliders_bkp.ibd' OS error: 103
2025-06-10T12:22:20.155610Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.155899Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.156342Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_revslider_sliders_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.156955Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_revslider_sliders_bkp` because it could not be opened.
2025-06-10T12:22:20.157395Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.157735Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.158012Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.158421Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_revslider_slides.ibd' OS error: 103
2025-06-10T12:22:20.158792Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.159056Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.159475Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_revslider_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.160312Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_revslider_slides` because it could not be opened.
2025-06-10T12:22:20.160830Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.161110Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.161392Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.161826Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_revslider_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:20.162199Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.162470Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.162924Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_revslider_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.163520Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_revslider_slides_bkp` because it could not be opened.
2025-06-10T12:22:20.163984Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.164250Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.164523Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.164964Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_revslider_static_slides.ibd' OS error: 103
2025-06-10T12:22:20.165326Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.165664Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.166097Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_revslider_static_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.166899Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_revslider_static_slides` because it could not be opened.
2025-06-10T12:22:20.167341Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.167629Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.167902Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.168261Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_revslider_static_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:20.168705Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.169003Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.169424Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_revslider_static_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.170129Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_revslider_static_slides_bkp` because it could not be opened.
2025-06-10T12:22:20.170643Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.170952Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.171208Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.171638Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_rich_web_icons.ibd' OS error: 103
2025-06-10T12:22:20.171966Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.172216Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.172666Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_rich_web_icons`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.173290Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_rich_web_icons` because it could not be opened.
2025-06-10T12:22:20.173724Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.173980Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.174236Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.174860Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_rich_web_timeline_manager.ibd' OS error: 103
2025-06-10T12:22:20.175213Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.175464Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.175946Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_rich_web_timeline_manager`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.176522Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_rich_web_timeline_manager` because it could not be opened.
2025-06-10T12:22:20.177130Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.177380Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.177724Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.178091Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_rich_web_timeline_options.ibd' OS error: 103
2025-06-10T12:22:20.178440Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.178785Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.179443Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_rich_web_timeline_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.180114Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_rich_web_timeline_options` because it could not be opened.
2025-06-10T12:22:20.180635Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.180919Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.181198Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.181614Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_rich_web_timeline_short_options.ibd' OS error: 103
2025-06-10T12:22:20.181993Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.182254Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.182692Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_rich_web_timeline_short_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.183300Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_rich_web_timeline_short_options` because it could not be opened.
2025-06-10T12:22:20.183832Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.184109Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.184447Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.184923Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_rich_web_timeline_style_options.ibd' OS error: 103
2025-06-10T12:22:20.185619Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.186046Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.186674Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_rich_web_timeline_style_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.187325Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_rich_web_timeline_style_options` because it could not be opened.
2025-06-10T12:22:20.187886Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.188147Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.188405Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.188900Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_rich_web_timeline_style_options_2.ibd' OS error: 103
2025-06-10T12:22:20.189261Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.189608Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.190012Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_rich_web_timeline_style_options_2`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.190698Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_rich_web_timeline_style_options_2` because it could not be opened.
2025-06-10T12:22:20.191164Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.191502Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.191797Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.192170Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:20.192597Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.192867Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.193284Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.194279Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:20.194755Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.195008Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.195279Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.195685Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:20.196017Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.196276Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.196707Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.197268Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:20.197697Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.197955Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.198221Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.198625Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:20.199128Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.199445Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.199866Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.200443Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_termmeta` because it could not be opened.
2025-06-10T12:22:20.201003Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.201365Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.201723Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.202114Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_terms.ibd' OS error: 103
2025-06-10T12:22:20.202459Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.202794Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.203187Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.203819Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_terms` because it could not be opened.
2025-06-10T12:22:20.204183Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.204549Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.204888Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.205501Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:20.205847Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.206101Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.206565Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.207107Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_usermeta` because it could not be opened.
2025-06-10T12:22:20.207555Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.207812Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.208070Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.208486Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_users.ibd' OS error: 103
2025-06-10T12:22:20.208803Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.209053Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.209605Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.210209Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_users` because it could not be opened.
2025-06-10T12:22:20.210666Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.210920Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.211351Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.211777Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_wfblockediplog.ibd' OS error: 103
2025-06-10T12:22:20.212111Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.212458Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.212861Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_wfblockediplog`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.213483Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_wfblockediplog` because it could not be opened.
2025-06-10T12:22:20.213894Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.214210Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.214530Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.214897Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_wfblocks7.ibd' OS error: 103
2025-06-10T12:22:20.215218Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.215597Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.216293Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_wfblocks7`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.216999Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_wfblocks7` because it could not be opened.
2025-06-10T12:22:20.218345Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.218637Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.218917Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.219362Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_wfconfig.ibd' OS error: 103
2025-06-10T12:22:20.219704Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.219967Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.220449Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_wfconfig`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.221017Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_wfconfig` because it could not be opened.
2025-06-10T12:22:20.221482Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.221751Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.222035Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.222488Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_wfcrawlers.ibd' OS error: 103
2025-06-10T12:22:20.222828Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.223100Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.223627Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_wfcrawlers`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.224212Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_wfcrawlers` because it could not be opened.
2025-06-10T12:22:20.224730Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.225104Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.225403Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.225793Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_wffilechanges.ibd' OS error: 103
2025-06-10T12:22:20.226134Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.226453Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.226868Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_wffilechanges`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.227488Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_wffilechanges` because it could not be opened.
2025-06-10T12:22:20.227887Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.228150Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.228465Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.228848Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_wffilemods.ibd' OS error: 103
2025-06-10T12:22:20.229181Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.229510Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.229921Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_wffilemods`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.230564Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_wffilemods` because it could not be opened.
2025-06-10T12:22:20.230951Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.231215Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.231561Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.231945Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_wfhits.ibd' OS error: 103
2025-06-10T12:22:20.232363Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.232636Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.233052Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_wfhits`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.233679Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_wfhits` because it could not be opened.
2025-06-10T12:22:20.234057Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.234398Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.234684Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.235075Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_wfhoover.ibd' OS error: 103
2025-06-10T12:22:20.235472Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.235735Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.236145Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_wfhoover`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.236766Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_wfhoover` because it could not be opened.
2025-06-10T12:22:20.237141Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.237463Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.237876Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.238319Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_wfissues.ibd' OS error: 103
2025-06-10T12:22:20.238655Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.238917Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.239385Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_wfissues`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.239947Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_wfissues` because it could not be opened.
2025-06-10T12:22:20.240384Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.240674Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.240976Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.241380Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_wfknownfilelist.ibd' OS error: 103
2025-06-10T12:22:20.241724Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.241984Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.242427Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_wfknownfilelist`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.243010Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_wfknownfilelist` because it could not be opened.
2025-06-10T12:22:20.243545Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.243862Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.244137Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.244536Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_wflivetraffichuman.ibd' OS error: 103
2025-06-10T12:22:20.244884Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.245236Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.245680Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_wflivetraffichuman`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.246334Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_wflivetraffichuman` because it could not be opened.
2025-06-10T12:22:20.246768Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.247023Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.247374Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.247783Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_wflocs.ibd' OS error: 103
2025-06-10T12:22:20.248324Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.248615Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.249021Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_wflocs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.249634Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_wflocs` because it could not be opened.
2025-06-10T12:22:20.250072Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.250485Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.250798Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.251195Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_wflogins.ibd' OS error: 103
2025-06-10T12:22:20.251647Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.251917Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.252409Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_wflogins`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.252982Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_wflogins` because it could not be opened.
2025-06-10T12:22:20.253460Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.253776Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.254085Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.254497Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_wfls_2fa_secrets.ibd' OS error: 103
2025-06-10T12:22:20.254893Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.255175Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.255609Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_wfls_2fa_secrets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.256216Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_wfls_2fa_secrets` because it could not be opened.
2025-06-10T12:22:20.256744Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.257017Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.257559Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.258079Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_wfls_settings.ibd' OS error: 103
2025-06-10T12:22:20.258646Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.258908Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.259394Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_wfls_settings`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.260003Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_wfls_settings` because it could not be opened.
2025-06-10T12:22:20.260510Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.260878Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.261144Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.261666Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_wfnotifications.ibd' OS error: 103
2025-06-10T12:22:20.262006Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.262273Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.262737Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_wfnotifications`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.263326Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_wfnotifications` because it could not be opened.
2025-06-10T12:22:20.263806Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.264057Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.264371Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.264814Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_wfpendingissues.ibd' OS error: 103
2025-06-10T12:22:20.265146Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.265456Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.265847Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_wfpendingissues`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.266451Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_wfpendingissues` because it could not be opened.
2025-06-10T12:22:20.266824Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.267075Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.267381Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.267758Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_wfreversecache.ibd' OS error: 103
2025-06-10T12:22:20.268080Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.268394Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.268816Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_wfreversecache`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.269430Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_wfreversecache` because it could not be opened.
2025-06-10T12:22:20.269795Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.270044Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.270360Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.270717Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_wfsnipcache.ibd' OS error: 103
2025-06-10T12:22:20.271307Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.271612Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.272011Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_wfsnipcache`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.272705Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_wfsnipcache` because it could not be opened.
2025-06-10T12:22:20.273112Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.273452Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.273736Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.274119Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_wfstatus.ibd' OS error: 103
2025-06-10T12:22:20.274513Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.274852Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.275385Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_wfstatus`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.275961Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_wfstatus` because it could not be opened.
2025-06-10T12:22:20.276534Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.276810Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.277178Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.277690Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_wftrafficrates.ibd' OS error: 103
2025-06-10T12:22:20.278052Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.278342Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.278766Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_wftrafficrates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.279370Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_wftrafficrates` because it could not be opened.
2025-06-10T12:22:20.279805Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.280058Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.280419Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.280870Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_wpfm_backup.ibd' OS error: 103
2025-06-10T12:22:20.281335Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.281660Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.282115Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_wpfm_backup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.282734Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_wpfm_backup` because it could not be opened.
2025-06-10T12:22:20.283127Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.283651Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.284002Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.284464Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_wpgmza.ibd' OS error: 103
2025-06-10T12:22:20.284963Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.285581Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.286005Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_wpgmza`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.286650Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_wpgmza` because it could not be opened.
2025-06-10T12:22:20.287130Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.287403Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.287679Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.288091Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_wpgmza_circles.ibd' OS error: 103
2025-06-10T12:22:20.288516Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.288796Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.289311Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_wpgmza_circles`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.289868Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_wpgmza_circles` because it could not be opened.
2025-06-10T12:22:20.290469Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.290853Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.291160Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.291557Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_wpgmza_maps.ibd' OS error: 103
2025-06-10T12:22:20.291967Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.292322Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.292760Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_wpgmza_maps`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.293486Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_wpgmza_maps` because it could not be opened.
2025-06-10T12:22:20.293983Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.294301Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.294578Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.294964Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_wpgmza_polygon.ibd' OS error: 103
2025-06-10T12:22:20.295351Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.295615Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.296024Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_wpgmza_polygon`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.296630Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_wpgmza_polygon` because it could not be opened.
2025-06-10T12:22:20.297047Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.297332Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.297606Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.297991Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_wpgmza_polylines.ibd' OS error: 103
2025-06-10T12:22:20.298365Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.298650Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.299195Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_wpgmza_polylines`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.299762Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_wpgmza_polylines` because it could not be opened.
2025-06-10T12:22:20.300224Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.300478Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.300878Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.301370Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_wpgmza_rectangles.ibd' OS error: 103
2025-06-10T12:22:20.301768Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.302055Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.302552Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_wpgmza_rectangles`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.303170Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_wpgmza_rectangles` because it could not be opened.
2025-06-10T12:22:20.303595Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.303863Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.304162Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.304535Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_yoast_seo_links.ibd' OS error: 103
2025-06-10T12:22:20.304874Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.305206Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.305591Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_yoast_seo_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.306205Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_yoast_seo_links` because it could not be opened.
2025-06-10T12:22:20.306581Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.306834Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.307140Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.307513Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem15\wp_yoast_seo_meta.ibd' OS error: 103
2025-06-10T12:22:20.307831Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.308126Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.308526Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem15/wp_yoast_seo_meta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.309210Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem15/wp_yoast_seo_meta` because it could not be opened.
2025-06-10T12:22:20.309604Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.309854Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.310235Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.310644Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:20.311078Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.311403Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.311848Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.312501Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:20.313016Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.313397Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.314272Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.314975Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_comments.ibd' OS error: 103
2025-06-10T12:22:20.315381Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.315658Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.316110Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.316666Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_comments` because it could not be opened.
2025-06-10T12:22:20.317114Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.317376Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.317648Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.318053Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:20.318367Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.318627Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.319327Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.320041Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_fbv` because it could not be opened.
2025-06-10T12:22:20.320482Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.320758Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.321091Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.321498Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:20.321984Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.322411Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.322897Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.323470Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:20.323967Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.324239Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.324531Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.324964Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_gg_attributes.ibd' OS error: 103
2025-06-10T12:22:20.325300Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.325543Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.326045Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_gg_attributes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.326664Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_gg_attributes` because it could not be opened.
2025-06-10T12:22:20.327175Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.327432Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.327687Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.328147Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_gg_cdn.ibd' OS error: 103
2025-06-10T12:22:20.328451Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.328698Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.329165Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_gg_cdn`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.329690Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_gg_cdn` because it could not be opened.
2025-06-10T12:22:20.330155Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.330408Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.330666Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.331094Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_gg_folders.ibd' OS error: 103
2025-06-10T12:22:20.331413Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.331663Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.332114Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_gg_folders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.332682Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_gg_folders` because it could not be opened.
2025-06-10T12:22:20.333096Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.333348Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.333606Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.334038Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_gg_galleries.ibd' OS error: 103
2025-06-10T12:22:20.334356Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.334604Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.335042Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_gg_galleries`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.335591Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_gg_galleries` because it could not be opened.
2025-06-10T12:22:20.336071Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.336326Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.336582Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.336996Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_gg_galleries_excluded.ibd' OS error: 103
2025-06-10T12:22:20.337337Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.337589Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.338158Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_gg_galleries_excluded`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.338818Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_gg_galleries_excluded` because it could not be opened.
2025-06-10T12:22:20.339426Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.339698Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.340086Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.340490Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_gg_galleries_resources.ibd' OS error: 103
2025-06-10T12:22:20.340941Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.341265Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.341779Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_gg_galleries_resources`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.342523Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_gg_galleries_resources` because it could not be opened.
2025-06-10T12:22:20.343034Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.343354Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.343634Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.344100Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_gg_image_optimize.ibd' OS error: 103
2025-06-10T12:22:20.344680Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.344940Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.345643Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_gg_image_optimize`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.346670Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_gg_image_optimize` because it could not be opened.
2025-06-10T12:22:20.347354Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.347631Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.347928Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.348375Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_gg_membership_presets.ibd' OS error: 103
2025-06-10T12:22:20.348733Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.349027Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.349447Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_gg_membership_presets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.350075Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_gg_membership_presets` because it could not be opened.
2025-06-10T12:22:20.350494Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.350746Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.351064Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.351430Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_gg_photos.ibd' OS error: 103
2025-06-10T12:22:20.351752Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.352347Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.352788Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_gg_photos`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.353408Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_gg_photos` because it could not be opened.
2025-06-10T12:22:20.353905Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.354248Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.354538Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.354990Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_gg_photos_pos.ibd' OS error: 103
2025-06-10T12:22:20.355343Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.355599Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.356086Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_gg_photos_pos`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.356641Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_gg_photos_pos` because it could not be opened.
2025-06-10T12:22:20.357136Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.357439Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.357711Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.358175Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_gg_photos_settings.ibd' OS error: 103
2025-06-10T12:22:20.358658Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.359077Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.359513Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_gg_photos_settings`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.360213Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_gg_photos_settings` because it could not be opened.
2025-06-10T12:22:20.360629Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.361045Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.361515Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.361987Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_gg_settings_presets.ibd' OS error: 103
2025-06-10T12:22:20.362347Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.362606Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.363082Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_gg_settings_presets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.363644Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_gg_settings_presets` because it could not be opened.
2025-06-10T12:22:20.364111Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.364509Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.364767Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.365304Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_gg_settings_sets.ibd' OS error: 103
2025-06-10T12:22:20.365703Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.366063Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.366461Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_gg_settings_sets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.367102Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_gg_settings_sets` because it could not be opened.
2025-06-10T12:22:20.367503Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.367757Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.368081Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.368444Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_gg_stats.ibd' OS error: 103
2025-06-10T12:22:20.368756Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.369073Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.369462Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_gg_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.370098Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_gg_stats` because it could not be opened.
2025-06-10T12:22:20.370528Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.370779Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.371153Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.371781Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_gg_tags.ibd' OS error: 103
2025-06-10T12:22:20.372258Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.372640Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.373129Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_gg_tags`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.373759Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_gg_tags` because it could not be opened.
2025-06-10T12:22:20.374209Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.374478Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.374744Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.375183Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_links.ibd' OS error: 103
2025-06-10T12:22:20.375506Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.375766Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.376516Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.377454Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_links` because it could not be opened.
2025-06-10T12:22:20.378129Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.378530Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.379019Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.379576Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_newsletter.ibd' OS error: 103
2025-06-10T12:22:20.380175Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.380564Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.381220Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_newsletter`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.382188Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_newsletter` because it could not be opened.
2025-06-10T12:22:20.382845Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.383496Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.383760Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.384208Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_newsletter_emails.ibd' OS error: 103
2025-06-10T12:22:20.384540Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.384836Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.385244Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_newsletter_emails`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.385875Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_newsletter_emails` because it could not be opened.
2025-06-10T12:22:20.386394Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.386647Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.386977Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.387361Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_newsletter_sent.ibd' OS error: 103
2025-06-10T12:22:20.387685Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.388031Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.388506Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_newsletter_sent`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.389385Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_newsletter_sent` because it could not be opened.
2025-06-10T12:22:20.389883Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.390192Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.390463Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.391101Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_newsletter_stats.ibd' OS error: 103
2025-06-10T12:22:20.391479Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.391732Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.392930Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_newsletter_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.394068Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_newsletter_stats` because it could not be opened.
2025-06-10T12:22:20.395485Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.395986Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.396518Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.397165Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_newsletter_user_logs.ibd' OS error: 103
2025-06-10T12:22:20.397604Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.397880Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.398309Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_newsletter_user_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.398934Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_newsletter_user_logs` because it could not be opened.
2025-06-10T12:22:20.399646Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.400019Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.400364Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.400773Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_options.ibd' OS error: 103
2025-06-10T12:22:20.401103Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.401467Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.401980Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.402795Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_options` because it could not be opened.
2025-06-10T12:22:20.403376Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.403650Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.403909Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.404290Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_post_views.ibd' OS error: 103
2025-06-10T12:22:20.404714Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.404985Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.405434Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_post_views`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.406004Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_post_views` because it could not be opened.
2025-06-10T12:22:20.406765Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.407128Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.407453Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.407915Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:20.408250Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.408592Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.408983Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.409572Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_postmeta` because it could not be opened.
2025-06-10T12:22:20.410045Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.410341Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.410615Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.410997Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_posts.ibd' OS error: 103
2025-06-10T12:22:20.411351Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.411654Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.412097Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.412752Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_posts` because it could not be opened.
2025-06-10T12:22:20.413392Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.413661Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.413932Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.414350Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_revslider_css.ibd' OS error: 103
2025-06-10T12:22:20.414684Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.414944Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.415384Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_revslider_css`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.415957Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_revslider_css` because it could not be opened.
2025-06-10T12:22:20.416389Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.416653Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.416924Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.417376Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_revslider_css_bkp.ibd' OS error: 103
2025-06-10T12:22:20.417726Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.417987Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.418439Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_revslider_css_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.419208Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_revslider_css_bkp` because it could not be opened.
2025-06-10T12:22:20.419690Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.419952Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.420214Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.420709Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_revslider_layer_animations.ibd' OS error: 103
2025-06-10T12:22:20.421091Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.421425Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.421833Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_revslider_layer_animations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.422578Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_revslider_layer_animations` because it could not be opened.
2025-06-10T12:22:20.423133Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.423477Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.423867Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.424286Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_revslider_layer_animations_bkp.ibd' OS error: 103
2025-06-10T12:22:20.424697Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.425247Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.425639Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_revslider_layer_animations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.426728Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_revslider_layer_animations_bkp` because it could not be opened.
2025-06-10T12:22:20.427353Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.427620Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.427962Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.428349Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_revslider_navigations.ibd' OS error: 103
2025-06-10T12:22:20.428750Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.429057Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.429444Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_revslider_navigations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.430190Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_revslider_navigations` because it could not be opened.
2025-06-10T12:22:20.430610Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.430939Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.431236Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.431608Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_revslider_navigations_bkp.ibd' OS error: 103
2025-06-10T12:22:20.432105Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.432373Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.432877Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_revslider_navigations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.433469Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_revslider_navigations_bkp` because it could not be opened.
2025-06-10T12:22:20.434396Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.434690Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.435003Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.435473Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_revslider_sliders.ibd' OS error: 103
2025-06-10T12:22:20.435872Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.436142Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.436634Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_revslider_sliders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.437430Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_revslider_sliders` because it could not be opened.
2025-06-10T12:22:20.437931Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.438186Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.438444Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.439042Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_revslider_sliders_bkp.ibd' OS error: 103
2025-06-10T12:22:20.439448Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.439842Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.440254Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_revslider_sliders_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.440890Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_revslider_sliders_bkp` because it could not be opened.
2025-06-10T12:22:20.441379Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.441652Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.442018Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.442388Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_revslider_slides.ibd' OS error: 103
2025-06-10T12:22:20.442780Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.443049Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.443450Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_revslider_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.444107Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_revslider_slides` because it could not be opened.
2025-06-10T12:22:20.444520Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.444880Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.445145Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.445513Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_revslider_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:20.446033Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.446400Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.447053Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_revslider_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.447856Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_revslider_slides_bkp` because it could not be opened.
2025-06-10T12:22:20.448261Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.448517Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.448848Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.449215Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_revslider_static_slides.ibd' OS error: 103
2025-06-10T12:22:20.449559Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.449898Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.450347Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_revslider_static_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.450989Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_revslider_static_slides` because it could not be opened.
2025-06-10T12:22:20.451438Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.451766Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.452117Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.452567Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_revslider_static_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:20.453108Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.453494Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.454141Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_revslider_static_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.454784Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_revslider_static_slides_bkp` because it could not be opened.
2025-06-10T12:22:20.455238Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.455485Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.455879Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.456244Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:20.456770Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.457016Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.457891Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.458652Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:20.459689Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.460062Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.460351Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.460796Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:20.461177Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.461602Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.462034Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.462693Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:20.463177Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.463444Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.463731Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.464110Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:20.464439Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.464747Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.465158Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.465775Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_termmeta` because it could not be opened.
2025-06-10T12:22:20.466364Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.466739Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.467133Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.467603Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_terms.ibd' OS error: 103
2025-06-10T12:22:20.467960Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.468219Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.468767Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.469311Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_terms` because it could not be opened.
2025-06-10T12:22:20.469897Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.470323Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.470705Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.471758Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:20.472574Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.473087Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.473668Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.474402Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_usermeta` because it could not be opened.
2025-06-10T12:22:20.474928Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.475176Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.475429Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.475887Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_users.ibd' OS error: 103
2025-06-10T12:22:20.476189Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.476429Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.477124Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.477861Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_users` because it could not be opened.
2025-06-10T12:22:20.478375Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.478696Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.478964Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.479332Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_wfblockediplog.ibd' OS error: 103
2025-06-10T12:22:20.479750Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.480012Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.480421Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_wfblockediplog`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.481061Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_wfblockediplog` because it could not be opened.
2025-06-10T12:22:20.481561Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.481843Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.482095Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.482542Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_wfblocks7.ibd' OS error: 103
2025-06-10T12:22:20.482966Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.483228Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.483998Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_wfblocks7`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.484807Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_wfblocks7` because it could not be opened.
2025-06-10T12:22:20.485260Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.485603Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.485856Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.486220Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_wfconfig.ibd' OS error: 103
2025-06-10T12:22:20.486589Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.486835Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.487419Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_wfconfig`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.488141Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_wfconfig` because it could not be opened.
2025-06-10T12:22:20.488784Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.489735Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.490199Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.490772Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_wfcrawlers.ibd' OS error: 103
2025-06-10T12:22:20.491114Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.491491Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.491946Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_wfcrawlers`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.492614Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_wfcrawlers` because it could not be opened.
2025-06-10T12:22:20.493070Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.493386Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.493655Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.494077Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_wffilechanges.ibd' OS error: 103
2025-06-10T12:22:20.494414Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.494674Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.495105Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_wffilechanges`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.495680Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_wffilechanges` because it could not be opened.
2025-06-10T12:22:20.496169Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.496438Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.496709Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.497196Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_wffilemods.ibd' OS error: 103
2025-06-10T12:22:20.497552Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.497910Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.498494Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_wffilemods`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.499189Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_wffilemods` because it could not be opened.
2025-06-10T12:22:20.499687Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.500027Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.500285Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.500860Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_wfhits.ibd' OS error: 103
2025-06-10T12:22:20.501216Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.501475Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.501938Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_wfhits`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.502836Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_wfhits` because it could not be opened.
2025-06-10T12:22:20.503258Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.503512Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.503924Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.504299Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_wfhoover.ibd' OS error: 103
2025-06-10T12:22:20.504609Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.504982Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.505376Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_wfhoover`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.506086Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_wfhoover` because it could not be opened.
2025-06-10T12:22:20.506449Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.506699Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.507049Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.507411Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_wfissues.ibd' OS error: 103
2025-06-10T12:22:20.507808Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.508171Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.508584Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_wfissues`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.509157Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_wfissues` because it could not be opened.
2025-06-10T12:22:20.509530Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.509859Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.510129Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.510508Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_wfknownfilelist.ibd' OS error: 103
2025-06-10T12:22:20.510906Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.511166Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.511579Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_wfknownfilelist`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.512372Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_wfknownfilelist` because it could not be opened.
2025-06-10T12:22:20.512783Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.513111Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.513413Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.513960Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_wflivetraffichuman.ibd' OS error: 103
2025-06-10T12:22:20.514341Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.514594Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.515173Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_wflivetraffichuman`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.515793Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_wflivetraffichuman` because it could not be opened.
2025-06-10T12:22:20.516226Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.516489Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.516820Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.517267Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_wflocs.ibd' OS error: 103
2025-06-10T12:22:20.517599Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.517882Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.518298Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_wflocs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.518986Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_wflocs` because it could not be opened.
2025-06-10T12:22:20.519372Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.519622Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.520059Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.520558Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_wflogins.ibd' OS error: 103
2025-06-10T12:22:20.520872Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.521229Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.522464Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_wflogins`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.523106Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_wflogins` because it could not be opened.
2025-06-10T12:22:20.523584Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.523868Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.524206Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.524590Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_wfls_2fa_secrets.ibd' OS error: 103
2025-06-10T12:22:20.524998Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.525263Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.525677Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_wfls_2fa_secrets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.526321Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_wfls_2fa_secrets` because it could not be opened.
2025-06-10T12:22:20.526812Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.527169Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.527446Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.527860Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_wfls_settings.ibd' OS error: 103
2025-06-10T12:22:20.528333Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.528609Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.529185Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_wfls_settings`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.529787Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_wfls_settings` because it could not be opened.
2025-06-10T12:22:20.530549Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.530834Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.531178Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.531570Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_wfnotifications.ibd' OS error: 103
2025-06-10T12:22:20.531973Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.532234Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.532645Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_wfnotifications`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.533388Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_wfnotifications` because it could not be opened.
2025-06-10T12:22:20.533836Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.534189Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.534461Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.534841Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_wfpendingissues.ibd' OS error: 103
2025-06-10T12:22:20.535236Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.535501Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.535959Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_wfpendingissues`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.536536Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_wfpendingissues` because it could not be opened.
2025-06-10T12:22:20.536969Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.537234Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.537503Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.537924Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_wfreversecache.ibd' OS error: 103
2025-06-10T12:22:20.538321Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.538619Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.539287Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_wfreversecache`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.539926Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_wfreversecache` because it could not be opened.
2025-06-10T12:22:20.540336Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.540600Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.540910Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.541298Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_wfsnipcache.ibd' OS error: 103
2025-06-10T12:22:20.541639Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.542027Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.542465Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_wfsnipcache`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.543077Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_wfsnipcache` because it could not be opened.
2025-06-10T12:22:20.543485Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.543751Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.544075Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.544452Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_wfstatus.ibd' OS error: 103
2025-06-10T12:22:20.544777Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.545092Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.545497Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_wfstatus`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.546119Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_wfstatus` because it could not be opened.
2025-06-10T12:22:20.546517Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.546780Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.547116Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.547500Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_wftrafficrates.ibd' OS error: 103
2025-06-10T12:22:20.547890Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.548165Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.548594Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_wftrafficrates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.549316Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_wftrafficrates` because it could not be opened.
2025-06-10T12:22:20.549753Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.550090Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.550362Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.550738Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_wpfm_backup.ibd' OS error: 103
2025-06-10T12:22:20.551139Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.551399Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.551805Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_wpfm_backup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.552456Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_wpfm_backup` because it could not be opened.
2025-06-10T12:22:20.552880Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.553532Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.554263Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.554891Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_wpgmza.ibd' OS error: 103
2025-06-10T12:22:20.555247Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.555533Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.555999Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_wpgmza`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.556578Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_wpgmza` because it could not be opened.
2025-06-10T12:22:20.556977Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.557243Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.557581Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.557960Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_wpgmza_circles.ibd' OS error: 103
2025-06-10T12:22:20.558300Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.558616Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.559040Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_wpgmza_circles`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.559717Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_wpgmza_circles` because it could not be opened.
2025-06-10T12:22:20.560177Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.560555Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.560834Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.561224Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_wpgmza_maps.ibd' OS error: 103
2025-06-10T12:22:20.561660Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.562038Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.562850Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_wpgmza_maps`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.563782Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_wpgmza_maps` because it could not be opened.
2025-06-10T12:22:20.564261Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.564579Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.564856Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.565267Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_wpgmza_polygon.ibd' OS error: 103
2025-06-10T12:22:20.565681Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.565955Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.566415Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_wpgmza_polygon`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.567143Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_wpgmza_polygon` because it could not be opened.
2025-06-10T12:22:20.567606Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.567877Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.568151Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.568571Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_wpgmza_polylines.ibd' OS error: 103
2025-06-10T12:22:20.568924Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.569184Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.569640Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_wpgmza_polylines`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.570220Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_wpgmza_polylines` because it could not be opened.
2025-06-10T12:22:20.570628Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.570897Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.571170Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.571593Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_wpgmza_rectangles.ibd' OS error: 103
2025-06-10T12:22:20.571943Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.572205Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.572657Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_wpgmza_rectangles`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.573252Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_wpgmza_rectangles` because it could not be opened.
2025-06-10T12:22:20.573699Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.573965Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.574237Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.574658Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_yoast_seo_links.ibd' OS error: 103
2025-06-10T12:22:20.575004Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.575384Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.575816Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_yoast_seo_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.576500Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_yoast_seo_links` because it could not be opened.
2025-06-10T12:22:20.577005Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.577290Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.577592Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.577979Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem16\wp_yoast_seo_meta.ibd' OS error: 103
2025-06-10T12:22:20.578641Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.578986Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.579435Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem16/wp_yoast_seo_meta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.580100Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem16/wp_yoast_seo_meta` because it could not be opened.
2025-06-10T12:22:20.580588Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.580857Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.581132Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.581639Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:20.582066Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.582371Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.582842Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.583463Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:20.583879Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.584191Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.584504Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.584962Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_comments.ibd' OS error: 103
2025-06-10T12:22:20.585299Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.586016Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.586559Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.587413Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_comments` because it could not be opened.
2025-06-10T12:22:20.587933Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.588388Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.588671Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.589075Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:20.589414Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.589681Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.590099Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.590696Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_fbv` because it could not be opened.
2025-06-10T12:22:20.591128Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.591433Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.591848Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.592275Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:20.592687Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.593056Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.593561Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.594277Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:20.594841Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.595111Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.595417Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.595800Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_gg_attributes.ibd' OS error: 103
2025-06-10T12:22:20.596140Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.596438Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.596855Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_gg_attributes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.597520Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_gg_attributes` because it could not be opened.
2025-06-10T12:22:20.598071Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.598335Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.598699Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.599069Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_gg_cdn.ibd' OS error: 103
2025-06-10T12:22:20.599408Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.599706Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.600098Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_gg_cdn`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.600747Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_gg_cdn` because it could not be opened.
2025-06-10T12:22:20.601162Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.601458Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.601756Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.602118Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_gg_folders.ibd' OS error: 103
2025-06-10T12:22:20.602543Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.602790Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.603184Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_gg_folders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.603866Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_gg_folders` because it could not be opened.
2025-06-10T12:22:20.604280Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.604565Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.604854Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.605427Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_gg_galleries.ibd' OS error: 103
2025-06-10T12:22:20.605841Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.606108Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.606570Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_gg_galleries`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.607142Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_gg_galleries` because it could not be opened.
2025-06-10T12:22:20.607620Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.607887Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.608153Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.608580Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_gg_galleries_excluded.ibd' OS error: 103
2025-06-10T12:22:20.608937Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.609197Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.609644Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_gg_galleries_excluded`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.610225Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_gg_galleries_excluded` because it could not be opened.
2025-06-10T12:22:20.610705Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.610989Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.611259Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.611651Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_gg_galleries_resources.ibd' OS error: 103
2025-06-10T12:22:20.612012Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.612305Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.612874Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_gg_galleries_resources`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.613632Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_gg_galleries_resources` because it could not be opened.
2025-06-10T12:22:20.614055Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.614340Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.614630Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.615013Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_gg_image_optimize.ibd' OS error: 103
2025-06-10T12:22:20.615388Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.615654Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.616061Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_gg_image_optimize`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.616686Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_gg_image_optimize` because it could not be opened.
2025-06-10T12:22:20.617109Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.617402Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.617742Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.618162Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_gg_membership_presets.ibd' OS error: 103
2025-06-10T12:22:20.618542Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.618810Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.619200Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_gg_membership_presets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.619862Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_gg_membership_presets` because it could not be opened.
2025-06-10T12:22:20.620265Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.620591Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.620850Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.621210Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_gg_photos.ibd' OS error: 103
2025-06-10T12:22:20.621583Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.621828Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.622220Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_gg_photos`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.622841Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_gg_photos` because it could not be opened.
2025-06-10T12:22:20.623202Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.623542Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.624032Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.624517Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_gg_photos_pos.ibd' OS error: 103
2025-06-10T12:22:20.624849Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.625170Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.625684Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_gg_photos_pos`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.626232Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_gg_photos_pos` because it could not be opened.
2025-06-10T12:22:20.627042Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.627568Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.627962Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.628653Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_gg_photos_settings.ibd' OS error: 103
2025-06-10T12:22:20.629243Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.629737Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.630637Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_gg_photos_settings`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.631237Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_gg_photos_settings` because it could not be opened.
2025-06-10T12:22:20.631760Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.632029Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.632371Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.632748Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_gg_settings_presets.ibd' OS error: 103
2025-06-10T12:22:20.633094Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.633413Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.633942Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_gg_settings_presets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.634991Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_gg_settings_presets` because it could not be opened.
2025-06-10T12:22:20.635804Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.636193Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.636542Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.636970Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_gg_settings_sets.ibd' OS error: 103
2025-06-10T12:22:20.637374Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.637790Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.638232Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_gg_settings_sets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.638868Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_gg_settings_sets` because it could not be opened.
2025-06-10T12:22:20.639328Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.639629Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.639895Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.640273Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_gg_stats.ibd' OS error: 103
2025-06-10T12:22:20.640619Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.640880Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.641292Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_gg_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.641982Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_gg_stats` because it could not be opened.
2025-06-10T12:22:20.642458Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.642734Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.643004Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.643425Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_gg_tags.ibd' OS error: 103
2025-06-10T12:22:20.643761Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.644024Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.644485Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_gg_tags`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.645049Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_gg_tags` because it could not be opened.
2025-06-10T12:22:20.645457Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.645722Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.645992Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.646382Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_links.ibd' OS error: 103
2025-06-10T12:22:20.646758Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.647016Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.647448Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.647993Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_links` because it could not be opened.
2025-06-10T12:22:20.648387Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.648664Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.648935Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.649374Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_newsletter.ibd' OS error: 103
2025-06-10T12:22:20.649705Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.649960Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.650630Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_newsletter`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.651240Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_newsletter` because it could not be opened.
2025-06-10T12:22:20.651663Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.651927Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.652242Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.652620Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_newsletter_emails.ibd' OS error: 103
2025-06-10T12:22:20.652965Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.653267Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.653673Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_newsletter_emails`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.654306Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_newsletter_emails` because it could not be opened.
2025-06-10T12:22:20.654739Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.655001Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.655338Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.655722Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_newsletter_sent.ibd' OS error: 103
2025-06-10T12:22:20.656102Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.656365Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.656944Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_newsletter_sent`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.657735Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_newsletter_sent` because it could not be opened.
2025-06-10T12:22:20.658304Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.658582Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.658895Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.659354Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_newsletter_stats.ibd' OS error: 103
2025-06-10T12:22:20.659723Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.659975Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.660433Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_newsletter_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.661057Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_newsletter_stats` because it could not be opened.
2025-06-10T12:22:20.661597Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.661961Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.662304Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.662697Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_newsletter_user_logs.ibd' OS error: 103
2025-06-10T12:22:20.663076Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.663341Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.663770Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_newsletter_user_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.664411Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_newsletter_user_logs` because it could not be opened.
2025-06-10T12:22:20.664894Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.665157Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.665577Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.666016Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_options.ibd' OS error: 103
2025-06-10T12:22:20.666343Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.666732Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.667142Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.667738Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_options` because it could not be opened.
2025-06-10T12:22:20.668206Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.668471Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.668763Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.669142Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_post_views.ibd' OS error: 103
2025-06-10T12:22:20.669490Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.669750Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.670341Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_post_views`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.670923Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_post_views` because it could not be opened.
2025-06-10T12:22:20.671609Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.671870Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.672336Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.672857Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:20.673328Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.673581Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.673983Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.674836Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_postmeta` because it could not be opened.
2025-06-10T12:22:20.675458Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.675764Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.676040Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.676567Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_posts.ibd' OS error: 103
2025-06-10T12:22:20.676904Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.677476Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.677930Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.678505Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_posts` because it could not be opened.
2025-06-10T12:22:20.678977Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.679310Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.679591Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.679971Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_revslider_css.ibd' OS error: 103
2025-06-10T12:22:20.680342Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.680604Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.681015Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_revslider_css`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.681613Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_revslider_css` because it could not be opened.
2025-06-10T12:22:20.682026Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.682326Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.682596Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.682973Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_revslider_css_bkp.ibd' OS error: 103
2025-06-10T12:22:20.683349Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.683747Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.684224Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_revslider_css_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.684832Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_revslider_css_bkp` because it could not be opened.
2025-06-10T12:22:20.685327Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.685692Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.685994Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.686432Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_revslider_layer_animations.ibd' OS error: 103
2025-06-10T12:22:20.686784Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.687034Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.687505Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_revslider_layer_animations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.688079Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_revslider_layer_animations` because it could not be opened.
2025-06-10T12:22:20.688601Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.688851Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.689109Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.689535Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_revslider_layer_animations_bkp.ibd' OS error: 103
2025-06-10T12:22:20.689887Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.690349Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.690771Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_revslider_layer_animations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.691420Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_revslider_layer_animations_bkp` because it could not be opened.
2025-06-10T12:22:20.691850Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.692103Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.692526Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.692959Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_revslider_navigations.ibd' OS error: 103
2025-06-10T12:22:20.693449Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.693869Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.694337Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_revslider_navigations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.694903Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_revslider_navigations` because it could not be opened.
2025-06-10T12:22:20.695402Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.695668Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.695926Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.696447Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_revslider_navigations_bkp.ibd' OS error: 103
2025-06-10T12:22:20.696924Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.697205Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.697761Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_revslider_navigations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.698866Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_revslider_navigations_bkp` because it could not be opened.
2025-06-10T12:22:20.699484Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.699755Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.700157Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.700568Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_revslider_sliders.ibd' OS error: 103
2025-06-10T12:22:20.700935Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.701226Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.701650Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_revslider_sliders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.702295Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_revslider_sliders` because it could not be opened.
2025-06-10T12:22:20.702808Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.703070Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.703408Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.703818Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_revslider_sliders_bkp.ibd' OS error: 103
2025-06-10T12:22:20.704245Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.704546Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.704961Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_revslider_sliders_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.705663Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_revslider_sliders_bkp` because it could not be opened.
2025-06-10T12:22:20.706553Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.706976Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.707388Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.707933Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_revslider_slides.ibd' OS error: 103
2025-06-10T12:22:20.708438Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.708744Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.709189Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_revslider_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.709805Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_revslider_slides` because it could not be opened.
2025-06-10T12:22:20.710330Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.710587Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.710844Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.711320Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_revslider_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:20.711667Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.711917Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.712420Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_revslider_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.712980Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_revslider_slides_bkp` because it could not be opened.
2025-06-10T12:22:20.713660Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.713914Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.714248Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.714622Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_revslider_static_slides.ibd' OS error: 103
2025-06-10T12:22:20.714965Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.715375Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.715766Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_revslider_static_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.716469Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_revslider_static_slides` because it could not be opened.
2025-06-10T12:22:20.716861Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.717111Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.717487Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.717862Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_revslider_static_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:20.718376Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.718631Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.719202Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_revslider_static_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.719794Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_revslider_static_slides_bkp` because it could not be opened.
2025-06-10T12:22:20.720318Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.720644Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.720919Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.721326Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:20.721674Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.721931Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.722391Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.722965Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:20.723490Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.723796Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.724180Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.724637Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:20.725011Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.725336Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.725828Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.726488Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:20.726908Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.727243Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.727571Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.727975Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:20.728433Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.729066Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.729752Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.730745Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_termmeta` because it could not be opened.
2025-06-10T12:22:20.731539Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.731889Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.732340Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.732952Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_terms.ibd' OS error: 103
2025-06-10T12:22:20.733315Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.733636Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.734052Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.734665Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_terms` because it could not be opened.
2025-06-10T12:22:20.735107Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.735392Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.735704Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.736088Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:20.736424Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.736739Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.737161Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.737787Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_usermeta` because it could not be opened.
2025-06-10T12:22:20.738358Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.738722Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.739001Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.739614Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_users.ibd' OS error: 103
2025-06-10T12:22:20.739960Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.740225Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.740676Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.741225Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_users` because it could not be opened.
2025-06-10T12:22:20.741671Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.741945Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.742217Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.742635Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_wfblockediplog.ibd' OS error: 103
2025-06-10T12:22:20.743006Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.743256Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.743719Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_wfblockediplog`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.744345Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_wfblockediplog` because it could not be opened.
2025-06-10T12:22:20.744804Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.745055Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.745350Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.745793Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_wfblocks7.ibd' OS error: 103
2025-06-10T12:22:20.746104Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.746436Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.747029Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_wfblocks7`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.747745Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_wfblocks7` because it could not be opened.
2025-06-10T12:22:20.748326Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.748782Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.749168Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.749730Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_wfconfig.ibd' OS error: 103
2025-06-10T12:22:20.750065Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.750311Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.750771Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_wfconfig`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.751314Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_wfconfig` because it could not be opened.
2025-06-10T12:22:20.752138Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.752430Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.752753Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.753137Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_wfcrawlers.ibd' OS error: 103
2025-06-10T12:22:20.753472Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.753793Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.754217Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_wfcrawlers`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.754868Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_wfcrawlers` because it could not be opened.
2025-06-10T12:22:20.755267Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.755586Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.755860Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.756307Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_wffilechanges.ibd' OS error: 103
2025-06-10T12:22:20.756724Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.756989Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.757395Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_wffilechanges`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.758043Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_wffilechanges` because it could not be opened.
2025-06-10T12:22:20.758687Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.758981Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.759443Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.760992Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_wffilemods.ibd' OS error: 103
2025-06-10T12:22:20.762544Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.762852Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.763337Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_wffilemods`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.764172Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_wffilemods` because it could not be opened.
2025-06-10T12:22:20.764634Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.764907Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.765226Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.765610Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_wfhits.ibd' OS error: 103
2025-06-10T12:22:20.765932Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.766223Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.766636Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_wfhits`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.767244Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_wfhits` because it could not be opened.
2025-06-10T12:22:20.767798Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.768118Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.768406Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.768801Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_wfhoover.ibd' OS error: 103
2025-06-10T12:22:20.769202Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.769490Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.769917Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_wfhoover`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.770576Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_wfhoover` because it could not be opened.
2025-06-10T12:22:20.771055Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.771328Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.771599Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.771977Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_wfissues.ibd' OS error: 103
2025-06-10T12:22:20.772350Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.772614Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.773056Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_wfissues`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.773647Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_wfissues` because it could not be opened.
2025-06-10T12:22:20.774061Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.774354Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.774657Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.775089Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_wfknownfilelist.ibd' OS error: 103
2025-06-10T12:22:20.775440Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.775705Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.776170Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_wfknownfilelist`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.776745Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_wfknownfilelist` because it could not be opened.
2025-06-10T12:22:20.777228Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.777496Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.777767Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.778212Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_wflivetraffichuman.ibd' OS error: 103
2025-06-10T12:22:20.778563Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.778823Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.779306Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_wflivetraffichuman`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.779883Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_wflivetraffichuman` because it could not be opened.
2025-06-10T12:22:20.780526Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.780794Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.781138Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.781549Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_wflocs.ibd' OS error: 103
2025-06-10T12:22:20.781875Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.782192Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.782604Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_wflocs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.783226Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_wflocs` because it could not be opened.
2025-06-10T12:22:20.783627Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.783891Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.784217Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.784598Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_wflogins.ibd' OS error: 103
2025-06-10T12:22:20.784920Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.785239Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.785650Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_wflogins`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.786281Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_wflogins` because it could not be opened.
2025-06-10T12:22:20.786664Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.786923Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.787298Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.787874Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_wfls_2fa_secrets.ibd' OS error: 103
2025-06-10T12:22:20.788451Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.788850Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.789551Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_wfls_2fa_secrets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.790482Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_wfls_2fa_secrets` because it could not be opened.
2025-06-10T12:22:20.791190Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.791576Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.792275Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.793644Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_wfls_settings.ibd' OS error: 103
2025-06-10T12:22:20.794310Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.794951Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.795682Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_wfls_settings`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.796473Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_wfls_settings` because it could not be opened.
2025-06-10T12:22:20.796993Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.797264Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.797539Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.797987Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_wfnotifications.ibd' OS error: 103
2025-06-10T12:22:20.798336Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.798669Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.799116Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_wfnotifications`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.799808Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_wfnotifications` because it could not be opened.
2025-06-10T12:22:20.800304Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.800568Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.800925Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.801309Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_wfpendingissues.ibd' OS error: 103
2025-06-10T12:22:20.802011Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.802317Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.802805Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_wfpendingissues`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.803373Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_wfpendingissues` because it could not be opened.
2025-06-10T12:22:20.803855Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.804110Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.804371Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.804804Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_wfreversecache.ibd' OS error: 103
2025-06-10T12:22:20.805129Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.805381Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.805899Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_wfreversecache`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.806478Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_wfreversecache` because it could not be opened.
2025-06-10T12:22:20.806959Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.807214Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.807473Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.807901Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_wfsnipcache.ibd' OS error: 103
2025-06-10T12:22:20.808251Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.808499Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.808984Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_wfsnipcache`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.809622Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_wfsnipcache` because it could not be opened.
2025-06-10T12:22:20.810011Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.810271Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.810531Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.810964Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_wfstatus.ibd' OS error: 103
2025-06-10T12:22:20.811296Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.811568Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.812014Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_wfstatus`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.812556Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_wfstatus` because it could not be opened.
2025-06-10T12:22:20.812979Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.813232Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.813494Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.813919Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_wftrafficrates.ibd' OS error: 103
2025-06-10T12:22:20.814263Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.814592Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.815012Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_wftrafficrates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.815761Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_wftrafficrates` because it could not be opened.
2025-06-10T12:22:20.816204Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.816482Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.816795Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.817182Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_wpfm_backup.ibd' OS error: 103
2025-06-10T12:22:20.817525Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.817832Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.818271Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_wpfm_backup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.818872Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_wpfm_backup` because it could not be opened.
2025-06-10T12:22:20.819281Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.819563Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.819882Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.820292Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_wpgmza.ibd' OS error: 103
2025-06-10T12:22:20.820661Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.820924Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.821479Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_wpgmza`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.822099Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_wpgmza` because it could not be opened.
2025-06-10T12:22:20.822587Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.822877Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.823164Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.823665Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_wpgmza_circles.ibd' OS error: 103
2025-06-10T12:22:20.825076Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.826302Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.826855Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_wpgmza_circles`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.827487Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_wpgmza_circles` because it could not be opened.
2025-06-10T12:22:20.827952Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.828224Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.828497Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.828925Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_wpgmza_maps.ibd' OS error: 103
2025-06-10T12:22:20.829592Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.830081Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.830534Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_wpgmza_maps`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.831191Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_wpgmza_maps` because it could not be opened.
2025-06-10T12:22:20.831752Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.832058Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.832333Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.832761Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_wpgmza_polygon.ibd' OS error: 103
2025-06-10T12:22:20.833118Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.833384Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.833852Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_wpgmza_polygon`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.834454Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_wpgmza_polygon` because it could not be opened.
2025-06-10T12:22:20.834927Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.835199Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.835478Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.835896Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_wpgmza_polylines.ibd' OS error: 103
2025-06-10T12:22:20.836241Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.836506Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.836957Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_wpgmza_polylines`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.837535Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_wpgmza_polylines` because it could not be opened.
2025-06-10T12:22:20.837969Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.838234Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.838505Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.838919Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_wpgmza_rectangles.ibd' OS error: 103
2025-06-10T12:22:20.839271Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.839533Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.839972Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_wpgmza_rectangles`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.840562Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_wpgmza_rectangles` because it could not be opened.
2025-06-10T12:22:20.841036Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.841330Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.841611Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.842123Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_wtl_cpts.ibd' OS error: 103
2025-06-10T12:22:20.842480Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.842797Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.843237Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_wtl_cpts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.843820Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_wtl_cpts` because it could not be opened.
2025-06-10T12:22:20.844233Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.844502Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.844808Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.845188Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_wtl_shortcodes.ibd' OS error: 103
2025-06-10T12:22:20.845532Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.845857Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.846345Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_wtl_shortcodes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.846959Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_wtl_shortcodes` because it could not be opened.
2025-06-10T12:22:20.847367Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.847635Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.847937Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.848323Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_yoast_seo_links.ibd' OS error: 103
2025-06-10T12:22:20.848696Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.849108Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.849566Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_yoast_seo_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.850213Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_yoast_seo_links` because it could not be opened.
2025-06-10T12:22:20.850673Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.850950Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.851226Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.851615Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem17\wp_yoast_seo_meta.ibd' OS error: 103
2025-06-10T12:22:20.851990Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.852253Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.852698Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem17/wp_yoast_seo_meta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.853343Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem17/wp_yoast_seo_meta` because it could not be opened.
2025-06-10T12:22:20.853822Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.854092Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.854366Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.854933Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_actionscheduler_actions.ibd' OS error: 103
2025-06-10T12:22:20.855462Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.855777Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.856230Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_actionscheduler_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.856921Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_actionscheduler_actions` because it could not be opened.
2025-06-10T12:22:20.857532Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.858004Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.858302Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.859068Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_actionscheduler_claims.ibd' OS error: 103
2025-06-10T12:22:20.859460Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.859772Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.860215Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_actionscheduler_claims`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.860808Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_actionscheduler_claims` because it could not be opened.
2025-06-10T12:22:20.861287Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.861558Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.861831Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.862242Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_actionscheduler_groups.ibd' OS error: 103
2025-06-10T12:22:20.862605Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.862927Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.863394Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_actionscheduler_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.864039Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_actionscheduler_groups` because it could not be opened.
2025-06-10T12:22:20.864715Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.864992Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.865299Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.865690Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_actionscheduler_logs.ibd' OS error: 103
2025-06-10T12:22:20.866054Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.866389Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.866826Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_actionscheduler_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.867462Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_actionscheduler_logs` because it could not be opened.
2025-06-10T12:22:20.867901Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.868253Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.868541Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.868932Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:20.869305Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.869712Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.870172Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.870748Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:20.871207Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.871482Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.871754Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.872184Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_comments.ibd' OS error: 103
2025-06-10T12:22:20.872513Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.872778Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.873252Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.873829Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_comments` because it could not be opened.
2025-06-10T12:22:20.874303Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.874583Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.874860Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.875277Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_csshero4.ibd' OS error: 103
2025-06-10T12:22:20.875778Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.876109Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.876529Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_csshero4`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.877124Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_csshero4` because it could not be opened.
2025-06-10T12:22:20.877604Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.877918Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.878316Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.878695Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:20.878997Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.879339Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.879769Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.880435Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_fbv` because it could not be opened.
2025-06-10T12:22:20.880837Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.881185Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.881508Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.882106Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:20.882536Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.882821Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.883269Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.883875Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:20.884348Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.884617Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.884886Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.885316Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_gg_attributes.ibd' OS error: 103
2025-06-10T12:22:20.885650Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.885909Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.886345Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_gg_attributes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.886921Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_gg_attributes` because it could not be opened.
2025-06-10T12:22:20.887372Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.887636Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.887905Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.888324Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_gg_cdn.ibd' OS error: 103
2025-06-10T12:22:20.888774Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.889105Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.889583Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_gg_cdn`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.890180Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_gg_cdn` because it could not be opened.
2025-06-10T12:22:20.890628Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.890899Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.891209Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.891747Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_gg_folders.ibd' OS error: 103
2025-06-10T12:22:20.892132Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.892399Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.892810Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_gg_folders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.893511Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_gg_folders` because it could not be opened.
2025-06-10T12:22:20.893901Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.894289Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.894549Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.895132Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_gg_galleries.ibd' OS error: 103
2025-06-10T12:22:20.895505Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.895754Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.896284Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_gg_galleries`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.896961Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_gg_galleries` because it could not be opened.
2025-06-10T12:22:20.897477Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.897738Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.898074Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.898540Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_gg_galleries_excluded.ibd' OS error: 103
2025-06-10T12:22:20.898883Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.899232Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.899648Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_gg_galleries_excluded`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.900304Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_gg_galleries_excluded` because it could not be opened.
2025-06-10T12:22:20.900800Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.901127Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.901404Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.901872Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_gg_galleries_resources.ibd' OS error: 103
2025-06-10T12:22:20.902273Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.902537Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.902949Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_gg_galleries_resources`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.903619Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_gg_galleries_resources` because it could not be opened.
2025-06-10T12:22:20.904214Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.904836Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.905148Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.905916Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_gg_image_optimize.ibd' OS error: 103
2025-06-10T12:22:20.906957Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.907256Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.907701Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_gg_image_optimize`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.908479Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_gg_image_optimize` because it could not be opened.
2025-06-10T12:22:20.909006Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.909308Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.909612Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.910027Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_gg_membership_presets.ibd' OS error: 103
2025-06-10T12:22:20.910432Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.910716Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.911174Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_gg_membership_presets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.911764Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_gg_membership_presets` because it could not be opened.
2025-06-10T12:22:20.912345Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.912627Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.912937Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.913420Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_gg_photos.ibd' OS error: 103
2025-06-10T12:22:20.913741Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.914008Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.914528Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_gg_photos`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.915208Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_gg_photos` because it could not be opened.
2025-06-10T12:22:20.915687Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.915953Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.916260Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.916645Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_gg_photos_pos.ibd' OS error: 103
2025-06-10T12:22:20.916985Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.917276Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.917757Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_gg_photos_pos`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.918399Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_gg_photos_pos` because it could not be opened.
2025-06-10T12:22:20.918822Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.919153Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.919438Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.919822Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_gg_photos_settings.ibd' OS error: 103
2025-06-10T12:22:20.920210Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.920469Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.920878Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_gg_photos_settings`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.921494Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_gg_photos_settings` because it could not be opened.
2025-06-10T12:22:20.921908Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.922199Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.922471Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.922989Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_gg_settings_presets.ibd' OS error: 103
2025-06-10T12:22:20.923388Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.923653Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.924095Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_gg_settings_presets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.924683Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_gg_settings_presets` because it could not be opened.
2025-06-10T12:22:20.925141Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.925408Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.925679Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.926096Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_gg_settings_sets.ibd' OS error: 103
2025-06-10T12:22:20.926442Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.926700Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.927140Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_gg_settings_sets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.927707Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_gg_settings_sets` because it could not be opened.
2025-06-10T12:22:20.928141Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.928404Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.928673Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.929243Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_gg_stats.ibd' OS error: 103
2025-06-10T12:22:20.929626Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.929930Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.930517Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_gg_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.931130Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_gg_stats` because it could not be opened.
2025-06-10T12:22:20.931546Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.931817Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.932127Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.932507Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_gg_tags.ibd' OS error: 103
2025-06-10T12:22:20.932840Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.933217Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.933713Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_gg_tags`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.934416Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_gg_tags` because it could not be opened.
2025-06-10T12:22:20.934805Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.935136Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.935429Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.935834Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_links.ibd' OS error: 103
2025-06-10T12:22:20.936651Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.936916Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.937384Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.938444Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_links` because it could not be opened.
2025-06-10T12:22:20.939059Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.939361Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.939652Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.940077Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_options.ibd' OS error: 103
2025-06-10T12:22:20.940424Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.940689Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.941119Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.941694Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_options` because it could not be opened.
2025-06-10T12:22:20.942136Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.942404Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.942677Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.943133Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_post_views.ibd' OS error: 103
2025-06-10T12:22:20.943505Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.943843Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.944280Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_post_views`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.945023Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_post_views` because it could not be opened.
2025-06-10T12:22:20.945483Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.945805Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.946097Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.946517Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:20.946888Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.947153Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.947580Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.948184Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_postmeta` because it could not be opened.
2025-06-10T12:22:20.948633Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.948959Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.949217Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.949613Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_postmeta_20210502.ibd' OS error: 103
2025-06-10T12:22:20.950009Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.950574Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.951219Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_postmeta_20210502`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.952050Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_postmeta_20210502` because it could not be opened.
2025-06-10T12:22:20.952503Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.952791Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.953070Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.953452Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_posts.ibd' OS error: 103
2025-06-10T12:22:20.953867Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.954118Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.954507Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.955127Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_posts` because it could not be opened.
2025-06-10T12:22:20.955495Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.955851Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.956283Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.956653Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_redirection_404.ibd' OS error: 103
2025-06-10T12:22:20.957191Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.957492Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.957939Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_redirection_404`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.958522Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_redirection_404` because it could not be opened.
2025-06-10T12:22:20.958992Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.959266Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.959537Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.959954Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_redirection_groups.ibd' OS error: 103
2025-06-10T12:22:20.960300Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.960562Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.961028Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_redirection_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.961580Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_redirection_groups` because it could not be opened.
2025-06-10T12:22:20.962070Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.962336Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.962607Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.963007Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_redirection_items.ibd' OS error: 103
2025-06-10T12:22:20.963445Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.963765Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.964247Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_redirection_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.965033Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_redirection_items` because it could not be opened.
2025-06-10T12:22:20.965569Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.965945Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.966198Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.966572Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_redirection_logs.ibd' OS error: 103
2025-06-10T12:22:20.967151Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.967415Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.968184Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_redirection_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.970442Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_redirection_logs` because it could not be opened.
2025-06-10T12:22:20.970967Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.971258Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.971538Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.972104Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_revslider_css.ibd' OS error: 103
2025-06-10T12:22:20.972457Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.972748Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.973168Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_revslider_css`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.973773Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_revslider_css` because it could not be opened.
2025-06-10T12:22:20.974197Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.974466Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.974785Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.975215Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_revslider_css_bkp.ibd' OS error: 103
2025-06-10T12:22:20.975782Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.976080Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.976489Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_revslider_css_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.977148Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_revslider_css_bkp` because it could not be opened.
2025-06-10T12:22:20.977787Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.978073Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.978497Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.978943Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_revslider_layer_animations.ibd' OS error: 103
2025-06-10T12:22:20.979406Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.979691Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.980161Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_revslider_layer_animations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.980781Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_revslider_layer_animations` because it could not be opened.
2025-06-10T12:22:20.981239Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.981501Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.981821Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.982232Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_revslider_layer_animations_bkp.ibd' OS error: 103
2025-06-10T12:22:20.982592Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.982901Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.983297Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_revslider_layer_animations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.983986Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_revslider_layer_animations_bkp` because it could not be opened.
2025-06-10T12:22:20.984476Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.984783Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.985305Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.985777Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_revslider_navigations.ibd' OS error: 103
2025-06-10T12:22:20.986205Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.986512Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.986962Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_revslider_navigations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.987642Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_revslider_navigations` because it could not be opened.
2025-06-10T12:22:20.988211Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.988572Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.988926Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.989352Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_revslider_navigations_bkp.ibd' OS error: 103
2025-06-10T12:22:20.989844Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.990110Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.990555Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_revslider_navigations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.991184Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_revslider_navigations_bkp` because it could not be opened.
2025-06-10T12:22:20.991636Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.991931Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.992201Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.992603Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_revslider_sliders.ibd' OS error: 103
2025-06-10T12:22:20.992964Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.993223Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.993635Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_revslider_sliders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.994259Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_revslider_sliders` because it could not be opened.
2025-06-10T12:22:20.994700Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.994970Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.995266Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.995667Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_revslider_sliders_bkp.ibd' OS error: 103
2025-06-10T12:22:20.996024Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.996291Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:20.996758Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_revslider_sliders_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:20.997357Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_revslider_sliders_bkp` because it could not be opened.
2025-06-10T12:22:20.997847Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:20.998116Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:20.998438Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:20.998902Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_revslider_slides.ibd' OS error: 103
2025-06-10T12:22:20.999333Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:20.999642Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.000386Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_revslider_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.001104Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_revslider_slides` because it could not be opened.
2025-06-10T12:22:21.001616Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.002067Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.002506Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.002912Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_revslider_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:21.003263Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.003535Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.004012Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_revslider_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.004596Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_revslider_slides_bkp` because it could not be opened.
2025-06-10T12:22:21.005131Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.005401Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.005676Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.006202Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_revslider_static_slides.ibd' OS error: 103
2025-06-10T12:22:21.006546Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.006797Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.007362Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_revslider_static_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.008127Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_revslider_static_slides` because it could not be opened.
2025-06-10T12:22:21.008581Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.008901Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.009220Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.009588Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_revslider_static_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:21.010120Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.010528Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.011049Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_revslider_static_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.011628Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_revslider_static_slides_bkp` because it could not be opened.
2025-06-10T12:22:21.012162Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.012416Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.012674Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.013113Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_rich_web_icons.ibd' OS error: 103
2025-06-10T12:22:21.013536Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.013804Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.014273Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_rich_web_icons`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.014884Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_rich_web_icons` because it could not be opened.
2025-06-10T12:22:21.015291Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.015544Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.015799Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.016254Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_rich_web_timeline_manager.ibd' OS error: 103
2025-06-10T12:22:21.016601Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.016972Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.017548Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_rich_web_timeline_manager`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.018256Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_rich_web_timeline_manager` because it could not be opened.
2025-06-10T12:22:21.018705Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.019014Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.019286Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.019668Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_rich_web_timeline_options.ibd' OS error: 103
2025-06-10T12:22:21.020075Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.020338Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.020745Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_rich_web_timeline_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.021771Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_rich_web_timeline_options` because it could not be opened.
2025-06-10T12:22:21.022291Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.022550Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.022849Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.023266Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_rich_web_timeline_short_options.ibd' OS error: 103
2025-06-10T12:22:21.023629Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.023960Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.024362Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_rich_web_timeline_short_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.025064Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_rich_web_timeline_short_options` because it could not be opened.
2025-06-10T12:22:21.025499Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.025751Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.026109Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.026511Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_rich_web_timeline_style_options.ibd' OS error: 103
2025-06-10T12:22:21.026910Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.027173Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.027580Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_rich_web_timeline_style_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.028264Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_rich_web_timeline_style_options` because it could not be opened.
2025-06-10T12:22:21.028902Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.029263Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.029572Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.030072Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_rich_web_timeline_style_options_2.ibd' OS error: 103
2025-06-10T12:22:21.030437Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.030685Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.031221Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_rich_web_timeline_style_options_2`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.031885Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_rich_web_timeline_style_options_2` because it could not be opened.
2025-06-10T12:22:21.032583Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.032870Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.033215Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.033851Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_sbi_instagram_feed_locator.ibd' OS error: 103
2025-06-10T12:22:21.034399Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.034711Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.035125Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_sbi_instagram_feed_locator`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.035851Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_sbi_instagram_feed_locator` because it could not be opened.
2025-06-10T12:22:21.036366Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.036639Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.036917Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.037332Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_sbi_instagram_feeds_posts.ibd' OS error: 103
2025-06-10T12:22:21.037697Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.037956Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.038450Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_sbi_instagram_feeds_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.039059Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_sbi_instagram_feeds_posts` because it could not be opened.
2025-06-10T12:22:21.039542Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.039812Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.040176Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.040849Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_sbi_instagram_posts.ibd' OS error: 103
2025-06-10T12:22:21.041609Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.042158Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.042723Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_sbi_instagram_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.043363Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_sbi_instagram_posts` because it could not be opened.
2025-06-10T12:22:21.043821Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.044092Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.044430Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.044822Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:21.045177Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.045475Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.045893Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.046524Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:21.046968Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.047522Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.047844Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.048299Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:21.048653Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.048916Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.049382Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.050025Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:21.050537Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.050872Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.051190Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.051625Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:21.052030Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.052354Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.053096Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.053740Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_termmeta` because it could not be opened.
2025-06-10T12:22:21.054208Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.054571Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.055020Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.055573Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_terms.ibd' OS error: 103
2025-06-10T12:22:21.055903Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.056154Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.056625Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.057200Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_terms` because it could not be opened.
2025-06-10T12:22:21.057697Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.057998Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.058336Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.058781Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_tm_taskmeta.ibd' OS error: 103
2025-06-10T12:22:21.059204Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.059496Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.059954Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_tm_taskmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.060653Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_tm_taskmeta` because it could not be opened.
2025-06-10T12:22:21.061294Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.061780Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.062083Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.062555Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_tm_tasks.ibd' OS error: 103
2025-06-10T12:22:21.062920Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.063237Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.063885Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_tm_tasks`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.064562Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_tm_tasks` because it could not be opened.
2025-06-10T12:22:21.065157Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.065522Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.065967Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.066372Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:21.066778Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.067157Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.067626Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.068558Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_usermeta` because it could not be opened.
2025-06-10T12:22:21.069165Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.069444Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.069741Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.070233Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_users.ibd' OS error: 103
2025-06-10T12:22:21.070593Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.070995Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.071502Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.072130Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_users` because it could not be opened.
2025-06-10T12:22:21.072681Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.072950Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.073361Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.073754Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_wc_admin_note_actions.ibd' OS error: 103
2025-06-10T12:22:21.074159Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.074448Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.074855Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_wc_admin_note_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.075534Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_wc_admin_note_actions` because it could not be opened.
2025-06-10T12:22:21.075997Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.076444Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.076778Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.077465Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_wc_admin_notes.ibd' OS error: 103
2025-06-10T12:22:21.078004Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.078482Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.078922Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_wc_admin_notes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.079604Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_wc_admin_notes` because it could not be opened.
2025-06-10T12:22:21.080081Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.080356Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.080609Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.080960Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_wc_category_lookup.ibd' OS error: 103
2025-06-10T12:22:21.081498Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.081799Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.082302Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_wc_category_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.082848Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_wc_category_lookup` because it could not be opened.
2025-06-10T12:22:21.083329Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.083574Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.083825Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.084420Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_wc_customer_lookup.ibd' OS error: 103
2025-06-10T12:22:21.084792Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.085116Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.085571Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_wc_customer_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.086222Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_wc_customer_lookup` because it could not be opened.
2025-06-10T12:22:21.086662Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.086931Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.087336Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.087721Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_wc_order_coupon_lookup.ibd' OS error: 103
2025-06-10T12:22:21.088098Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.088523Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.088948Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_wc_order_coupon_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.089645Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_wc_order_coupon_lookup` because it could not be opened.
2025-06-10T12:22:21.090101Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.090372Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.090805Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.091315Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_wc_order_product_lookup.ibd' OS error: 103
2025-06-10T12:22:21.091712Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.092118Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.092619Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_wc_order_product_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.093270Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_wc_order_product_lookup` because it could not be opened.
2025-06-10T12:22:21.093715Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.094090Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.094517Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.094932Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_wc_order_stats.ibd' OS error: 103
2025-06-10T12:22:21.095331Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.095577Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.095963Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_wc_order_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.096737Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_wc_order_stats` because it could not be opened.
2025-06-10T12:22:21.097247Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.097559Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.098051Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.098973Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_wc_order_tax_lookup.ibd' OS error: 103
2025-06-10T12:22:21.099615Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.100078Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.100731Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_wc_order_tax_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.101404Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_wc_order_tax_lookup` because it could not be opened.
2025-06-10T12:22:21.101909Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.102162Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.102427Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.102894Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_wc_product_meta_lookup.ibd' OS error: 103
2025-06-10T12:22:21.103273Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.103637Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.104048Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_wc_product_meta_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.104896Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_wc_product_meta_lookup` because it could not be opened.
2025-06-10T12:22:21.105712Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.106249Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.106675Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.107130Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_wc_reserved_stock.ibd' OS error: 103
2025-06-10T12:22:21.107567Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.107854Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.108282Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_wc_reserved_stock`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.108969Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_wc_reserved_stock` because it could not be opened.
2025-06-10T12:22:21.109449Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.109752Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.110025Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.110398Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_wc_tax_rate_classes.ibd' OS error: 103
2025-06-10T12:22:21.110795Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.111045Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.111438Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_wc_tax_rate_classes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.112061Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_wc_tax_rate_classes` because it could not be opened.
2025-06-10T12:22:21.112452Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.112752Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.113007Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.113486Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_wc_webhooks.ibd' OS error: 103
2025-06-10T12:22:21.113832Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.114082Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.114532Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_wc_webhooks`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.115092Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_wc_webhooks` because it could not be opened.
2025-06-10T12:22:21.115486Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.115758Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.116016Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.116379Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_woocommerce_api_keys.ibd' OS error: 103
2025-06-10T12:22:21.116828Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.117104Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.117739Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_woocommerce_api_keys`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.118306Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_woocommerce_api_keys` because it could not be opened.
2025-06-10T12:22:21.118808Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.119075Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.119334Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.119771Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_woocommerce_attribute_taxonomies.ibd' OS error: 103
2025-06-10T12:22:21.120135Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.120385Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.120837Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_woocommerce_attribute_taxonomies`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.121541Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_woocommerce_attribute_taxonomies` because it could not be opened.
2025-06-10T12:22:21.122021Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.122274Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.122612Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.123029Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_woocommerce_downloadable_product_permissions.ibd' OS error: 103
2025-06-10T12:22:21.123427Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.123811Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.124205Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_woocommerce_downloadable_product_permissions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.124880Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_woocommerce_downloadable_product_permissions` because it could not be opened.
2025-06-10T12:22:21.125335Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.125650Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.125970Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.126334Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_woocommerce_log.ibd' OS error: 103
2025-06-10T12:22:21.126723Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.126974Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.127369Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_woocommerce_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.127998Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_woocommerce_log` because it could not be opened.
2025-06-10T12:22:21.128435Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.128708Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.128979Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.129361Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_woocommerce_order_itemmeta.ibd' OS error: 103
2025-06-10T12:22:21.129759Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.130022Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.130460Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_woocommerce_order_itemmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.131076Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_woocommerce_order_itemmeta` because it could not be opened.
2025-06-10T12:22:21.131541Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.131806Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.132191Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.132629Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_woocommerce_order_items.ibd' OS error: 103
2025-06-10T12:22:21.133006Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.133270Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.133809Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_woocommerce_order_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.134414Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_woocommerce_order_items` because it could not be opened.
2025-06-10T12:22:21.134850Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.135113Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.135383Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.135796Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_woocommerce_payment_tokenmeta.ibd' OS error: 103
2025-06-10T12:22:21.136165Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.136463Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.136880Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_woocommerce_payment_tokenmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.137525Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_woocommerce_payment_tokenmeta` because it could not be opened.
2025-06-10T12:22:21.137954Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.138241Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.138560Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.138943Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_woocommerce_payment_tokens.ibd' OS error: 103
2025-06-10T12:22:21.139311Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.139609Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.140023Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_woocommerce_payment_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.140693Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_woocommerce_payment_tokens` because it could not be opened.
2025-06-10T12:22:21.141145Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.141442Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.141717Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.142100Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_woocommerce_sessions.ibd' OS error: 103
2025-06-10T12:22:21.142479Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.142745Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.143157Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_woocommerce_sessions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.143784Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_woocommerce_sessions` because it could not be opened.
2025-06-10T12:22:21.144765Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.145356Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.145736Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.146495Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_woocommerce_shipping_zone_locations.ibd' OS error: 103
2025-06-10T12:22:21.146896Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.147261Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.147702Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_woocommerce_shipping_zone_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.148376Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_woocommerce_shipping_zone_locations` because it could not be opened.
2025-06-10T12:22:21.148871Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.149172Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.149446Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.149834Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_woocommerce_shipping_zone_methods.ibd' OS error: 103
2025-06-10T12:22:21.150254Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.150522Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.150943Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_woocommerce_shipping_zone_methods`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.151645Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_woocommerce_shipping_zone_methods` because it could not be opened.
2025-06-10T12:22:21.152190Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.152691Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.152980Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.153393Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_woocommerce_shipping_zones.ibd' OS error: 103
2025-06-10T12:22:21.153794Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.154087Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.154516Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_woocommerce_shipping_zones`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.155164Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_woocommerce_shipping_zones` because it could not be opened.
2025-06-10T12:22:21.155615Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.155880Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.156184Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.156572Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_woocommerce_tax_rate_locations.ibd' OS error: 103
2025-06-10T12:22:21.156950Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.157252Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.157685Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_woocommerce_tax_rate_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.158317Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_woocommerce_tax_rate_locations` because it could not be opened.
2025-06-10T12:22:21.158776Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.159057Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.159333Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.159726Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_woocommerce_tax_rates.ibd' OS error: 103
2025-06-10T12:22:21.160113Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.160377Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.160794Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_woocommerce_tax_rates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.161418Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_woocommerce_tax_rates` because it could not be opened.
2025-06-10T12:22:21.161818Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.162108Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.162376Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.162759Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_wpgmza.ibd' OS error: 103
2025-06-10T12:22:21.163112Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.163371Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.163777Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_wpgmza`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.164451Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_wpgmza` because it could not be opened.
2025-06-10T12:22:21.164957Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.165276Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.165540Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.165902Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_wpgmza_circles.ibd' OS error: 103
2025-06-10T12:22:21.166371Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.166619Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.167047Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_wpgmza_circles`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.167665Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_wpgmza_circles` because it could not be opened.
2025-06-10T12:22:21.168135Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.168407Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.168665Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.169078Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_wpgmza_maps.ibd' OS error: 103
2025-06-10T12:22:21.169417Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.169666Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.170162Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_wpgmza_maps`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.171128Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_wpgmza_maps` because it could not be opened.
2025-06-10T12:22:21.171722Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.172204Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.172607Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.173225Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_wpgmza_polygon.ibd' OS error: 103
2025-06-10T12:22:21.173831Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.174225Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.174653Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_wpgmza_polygon`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.175333Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_wpgmza_polygon` because it could not be opened.
2025-06-10T12:22:21.175782Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.176106Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.176404Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.176813Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_wpgmza_polylines.ibd' OS error: 103
2025-06-10T12:22:21.177797Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.178481Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.180015Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_wpgmza_polylines`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.180632Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_wpgmza_polylines` because it could not be opened.
2025-06-10T12:22:21.181105Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.181380Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.181722Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.182135Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_wpgmza_rectangles.ibd' OS error: 103
2025-06-10T12:22:21.182488Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.182750Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.183207Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_wpgmza_rectangles`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.183804Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_wpgmza_rectangles` because it could not be opened.
2025-06-10T12:22:21.184305Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.184581Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.184856Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.185345Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:21.185709Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.186005Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.186552Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.187207Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:21.187643Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.187906Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.188210Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.188655Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:21.189049Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.189315Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.189723Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.190359Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:21.190755Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.191044Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.191312Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.191885Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:21.192283Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.192543Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.192989Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.193555Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:21.194087Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.194355Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.194613Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.195089Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem18\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:21.195446Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.195696Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.196186Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem18/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.196754Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem18/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:21.197525Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.197844Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.198233Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.198606Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_actionscheduler_actions.ibd' OS error: 103
2025-06-10T12:22:21.198979Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.199296Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.199730Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_actionscheduler_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.200429Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_actionscheduler_actions` because it could not be opened.
2025-06-10T12:22:21.201132Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.201437Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.201826Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.202285Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_actionscheduler_claims.ibd' OS error: 103
2025-06-10T12:22:21.202636Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.202891Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.203445Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_actionscheduler_claims`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.204115Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_actionscheduler_claims` because it could not be opened.
2025-06-10T12:22:21.204881Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.205261Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.205672Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.206132Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_actionscheduler_groups.ibd' OS error: 103
2025-06-10T12:22:21.206481Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.206726Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.207268Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_actionscheduler_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.208543Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_actionscheduler_groups` because it could not be opened.
2025-06-10T12:22:21.209470Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.210050Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.210780Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.211205Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_actionscheduler_logs.ibd' OS error: 103
2025-06-10T12:22:21.211560Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.211946Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.212544Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_actionscheduler_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.213156Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_actionscheduler_logs` because it could not be opened.
2025-06-10T12:22:21.213602Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.213932Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.214202Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.214583Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:21.214987Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.215258Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.215873Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.216590Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:21.217188Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.217449Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.217800Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.218370Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_comments.ibd' OS error: 103
2025-06-10T12:22:21.218801Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.219069Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.219502Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.220249Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_comments` because it could not be opened.
2025-06-10T12:22:21.220711Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.220980Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.221233Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.221592Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_csshero4.ibd' OS error: 103
2025-06-10T12:22:21.222218Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.222546Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.223078Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_csshero4`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.223684Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_csshero4` because it could not be opened.
2025-06-10T12:22:21.224082Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.224344Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.224673Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.225092Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:21.225410Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.225893Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.226344Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.226994Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_fbv` because it could not be opened.
2025-06-10T12:22:21.227374Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.227671Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.227950Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.228311Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:21.228695Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.228989Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.229444Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.230143Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:21.230551Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.230889Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.231149Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.231513Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_gg_attributes.ibd' OS error: 103
2025-06-10T12:22:21.231961Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.232304Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.232827Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_gg_attributes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.233440Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_gg_attributes` because it could not be opened.
2025-06-10T12:22:21.234033Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.234303Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.234571Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.235092Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_gg_cdn.ibd' OS error: 103
2025-06-10T12:22:21.235566Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.235867Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.236298Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_gg_cdn`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.236959Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_gg_cdn` because it could not be opened.
2025-06-10T12:22:21.237598Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.237946Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.238201Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.238563Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_gg_folders.ibd' OS error: 103
2025-06-10T12:22:21.239084Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.239363Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.239852Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_gg_folders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.240682Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_gg_folders` because it could not be opened.
2025-06-10T12:22:21.241310Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.242097Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.242362Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.243203Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_gg_galleries.ibd' OS error: 103
2025-06-10T12:22:21.243550Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.243889Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.244455Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_gg_galleries`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.245094Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_gg_galleries` because it could not be opened.
2025-06-10T12:22:21.245552Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.245884Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.246160Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.246743Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_gg_galleries_excluded.ibd' OS error: 103
2025-06-10T12:22:21.247155Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.247429Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.248013Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_gg_galleries_excluded`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.248646Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_gg_galleries_excluded` because it could not be opened.
2025-06-10T12:22:21.249191Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.249481Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.249836Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.250275Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_gg_galleries_resources.ibd' OS error: 103
2025-06-10T12:22:21.250654Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.250975Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.251391Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_gg_galleries_resources`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.252022Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_gg_galleries_resources` because it could not be opened.
2025-06-10T12:22:21.252460Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.252724Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.253037Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.253424Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_gg_image_optimize.ibd' OS error: 103
2025-06-10T12:22:21.253804Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.254069Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.254482Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_gg_image_optimize`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.255095Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_gg_image_optimize` because it could not be opened.
2025-06-10T12:22:21.255493Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.255786Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.256059Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.256441Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_gg_membership_presets.ibd' OS error: 103
2025-06-10T12:22:21.256826Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.257089Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.257519Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_gg_membership_presets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.258205Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_gg_membership_presets` because it could not be opened.
2025-06-10T12:22:21.258606Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.258947Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.259208Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.259601Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_gg_photos.ibd' OS error: 103
2025-06-10T12:22:21.260221Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.260518Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.261043Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_gg_photos`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.261615Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_gg_photos` because it could not be opened.
2025-06-10T12:22:21.262069Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.262336Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.262609Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.263040Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_gg_photos_pos.ibd' OS error: 103
2025-06-10T12:22:21.263377Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.263638Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.264118Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_gg_photos_pos`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.264689Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_gg_photos_pos` because it could not be opened.
2025-06-10T12:22:21.265139Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.265403Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.265678Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.266126Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_gg_photos_settings.ibd' OS error: 103
2025-06-10T12:22:21.266479Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.266791Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.267204Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_gg_photos_settings`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.267853Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_gg_photos_settings` because it could not be opened.
2025-06-10T12:22:21.268322Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.268591Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.268946Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.269332Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_gg_settings_presets.ibd' OS error: 103
2025-06-10T12:22:21.269732Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.270027Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.270465Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_gg_settings_presets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.271110Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_gg_settings_presets` because it could not be opened.
2025-06-10T12:22:21.271538Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.271873Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.272194Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.272600Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_gg_settings_sets.ibd' OS error: 103
2025-06-10T12:22:21.272970Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.273238Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.273652Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_gg_settings_sets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.274268Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_gg_settings_sets` because it could not be opened.
2025-06-10T12:22:21.274724Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.274996Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.275267Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.275651Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_gg_stats.ibd' OS error: 103
2025-06-10T12:22:21.276010Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.276276Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.276717Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_gg_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.277296Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_gg_stats` because it could not be opened.
2025-06-10T12:22:21.277700Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.278166Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.278471Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.278940Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_gg_tags.ibd' OS error: 103
2025-06-10T12:22:21.279325Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.279931Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.280591Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_gg_tags`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.281423Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_gg_tags` because it could not be opened.
2025-06-10T12:22:21.281907Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.282181Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.282455Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.282910Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_links.ibd' OS error: 103
2025-06-10T12:22:21.283244Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.283566Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.284152Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.284779Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_links` because it could not be opened.
2025-06-10T12:22:21.285211Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.285526Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.285821Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.286216Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_options.ibd' OS error: 103
2025-06-10T12:22:21.286624Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.286890Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.287309Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.287975Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_options` because it could not be opened.
2025-06-10T12:22:21.288418Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.288815Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.289102Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.289499Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_post_views.ibd' OS error: 103
2025-06-10T12:22:21.289890Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.290199Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.290651Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_post_views`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.291276Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_post_views` because it could not be opened.
2025-06-10T12:22:21.291727Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.292000Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.292279Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.292715Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:21.293065Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.293338Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.293771Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.294347Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_postmeta` because it could not be opened.
2025-06-10T12:22:21.295080Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.295378Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.295751Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.296165Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_postmeta_2.ibd' OS error: 103
2025-06-10T12:22:21.296544Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.296809Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.297417Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_postmeta_2`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.298016Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_postmeta_2` because it could not be opened.
2025-06-10T12:22:21.298419Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.298757Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.299033Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.299419Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_posts.ibd' OS error: 103
2025-06-10T12:22:21.299766Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.300030Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.300457Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.301049Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_posts` because it could not be opened.
2025-06-10T12:22:21.301522Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.301797Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.302069Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.302527Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_redirection_404.ibd' OS error: 103
2025-06-10T12:22:21.302965Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.303277Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.303718Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_redirection_404`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.304308Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_redirection_404` because it could not be opened.
2025-06-10T12:22:21.304804Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.305136Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.305414Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.305924Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_redirection_groups.ibd' OS error: 103
2025-06-10T12:22:21.306382Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.306680Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.307453Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_redirection_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.308054Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_redirection_groups` because it could not be opened.
2025-06-10T12:22:21.308580Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.308839Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.309096Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.309584Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_redirection_items.ibd' OS error: 103
2025-06-10T12:22:21.309920Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.310316Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.310832Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_redirection_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.311515Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_redirection_items` because it could not be opened.
2025-06-10T12:22:21.311958Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.312351Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.312631Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.313004Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_redirection_logs.ibd' OS error: 103
2025-06-10T12:22:21.313437Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.313715Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.314255Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_redirection_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.314981Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_redirection_logs` because it could not be opened.
2025-06-10T12:22:21.315616Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.315875Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.316242Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.316660Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_revslider_css.ibd' OS error: 103
2025-06-10T12:22:21.317009Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.317308Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.317727Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_revslider_css`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.318333Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_revslider_css` because it could not be opened.
2025-06-10T12:22:21.318744Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.319017Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.319387Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.319809Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_revslider_css_bkp.ibd' OS error: 103
2025-06-10T12:22:21.320183Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.320460Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.320878Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_revslider_css_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.321500Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_revslider_css_bkp` because it could not be opened.
2025-06-10T12:22:21.321925Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.322234Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.322511Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.322900Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_revslider_layer_animations.ibd' OS error: 103
2025-06-10T12:22:21.323311Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.323580Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.324000Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_revslider_layer_animations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.324648Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_revslider_layer_animations` because it could not be opened.
2025-06-10T12:22:21.325080Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.325383Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.325664Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.326083Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_revslider_layer_animations_bkp.ibd' OS error: 103
2025-06-10T12:22:21.326513Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.326781Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.327249Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_revslider_layer_animations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.327876Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_revslider_layer_animations_bkp` because it could not be opened.
2025-06-10T12:22:21.328394Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.328682Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.328962Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.329395Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_revslider_navigations.ibd' OS error: 103
2025-06-10T12:22:21.329781Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.330056Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.330634Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_revslider_navigations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.331283Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_revslider_navigations` because it could not be opened.
2025-06-10T12:22:21.331710Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.331968Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.332343Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.332751Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_revslider_navigations_bkp.ibd' OS error: 103
2025-06-10T12:22:21.333173Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.333440Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.333892Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_revslider_navigations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.334534Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_revslider_navigations_bkp` because it could not be opened.
2025-06-10T12:22:21.335000Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.335316Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.335576Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.335957Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_revslider_sliders.ibd' OS error: 103
2025-06-10T12:22:21.336407Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.336792Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.337221Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_revslider_sliders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.338409Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_revslider_sliders` because it could not be opened.
2025-06-10T12:22:21.339212Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.339500Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.339783Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.340241Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_revslider_sliders_bkp.ibd' OS error: 103
2025-06-10T12:22:21.340605Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.340941Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.341367Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_revslider_sliders_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.342057Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_revslider_sliders_bkp` because it could not be opened.
2025-06-10T12:22:21.342536Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.342805Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.343162Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.343553Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_revslider_slides.ibd' OS error: 103
2025-06-10T12:22:21.344021Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.344290Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.344769Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_revslider_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.345443Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_revslider_slides` because it could not be opened.
2025-06-10T12:22:21.346000Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.346315Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.346593Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.347029Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_revslider_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:21.347553Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.347833Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.348265Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_revslider_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.348890Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_revslider_slides_bkp` because it could not be opened.
2025-06-10T12:22:21.349322Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.349587Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.349891Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.350276Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_revslider_static_slides.ibd' OS error: 103
2025-06-10T12:22:21.350632Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.350918Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.351330Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_revslider_static_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.351953Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_revslider_static_slides` because it could not be opened.
2025-06-10T12:22:21.352358Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.352625Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.352920Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.353332Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_revslider_static_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:21.353744Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.354050Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.354470Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_revslider_static_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.355112Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_revslider_static_slides_bkp` because it could not be opened.
2025-06-10T12:22:21.355536Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.355853Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.356180Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.356565Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_rich_web_icons.ibd' OS error: 103
2025-06-10T12:22:21.356977Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.357243Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.357656Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_rich_web_icons`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.358284Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_rich_web_icons` because it could not be opened.
2025-06-10T12:22:21.358678Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.359014Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.359287Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.359667Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_rich_web_timeline_manager.ibd' OS error: 103
2025-06-10T12:22:21.360101Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.360479Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.360975Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_rich_web_timeline_manager`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.361581Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_rich_web_timeline_manager` because it could not be opened.
2025-06-10T12:22:21.362078Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.362353Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.362612Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.363043Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_rich_web_timeline_options.ibd' OS error: 103
2025-06-10T12:22:21.363406Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.363669Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.364116Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_rich_web_timeline_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.364695Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_rich_web_timeline_options` because it could not be opened.
2025-06-10T12:22:21.365147Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.365402Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.365661Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.366090Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_rich_web_timeline_short_options.ibd' OS error: 103
2025-06-10T12:22:21.366462Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.366720Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.367204Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_rich_web_timeline_short_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.367970Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_rich_web_timeline_short_options` because it could not be opened.
2025-06-10T12:22:21.368374Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.368623Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.368999Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.369376Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_rich_web_timeline_style_options.ibd' OS error: 103
2025-06-10T12:22:21.369738Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.370057Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.370512Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_rich_web_timeline_style_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.371238Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_rich_web_timeline_style_options` because it could not be opened.
2025-06-10T12:22:21.371907Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.372223Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.372479Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.372946Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_rich_web_timeline_style_options_2.ibd' OS error: 103
2025-06-10T12:22:21.373627Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.374075Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.374566Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_rich_web_timeline_style_options_2`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.375243Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_rich_web_timeline_style_options_2` because it could not be opened.
2025-06-10T12:22:21.375808Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.376089Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.376364Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.376775Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_sbi_instagram_feed_locator.ibd' OS error: 103
2025-06-10T12:22:21.377164Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.377429Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.378007Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_sbi_instagram_feed_locator`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.378632Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_sbi_instagram_feed_locator` because it could not be opened.
2025-06-10T12:22:21.379225Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.379591Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.379902Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.380298Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_sbi_instagram_feeds_posts.ibd' OS error: 103
2025-06-10T12:22:21.380673Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.381000Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.381426Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_sbi_instagram_feeds_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.382074Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_sbi_instagram_feeds_posts` because it could not be opened.
2025-06-10T12:22:21.382497Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.382791Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.383071Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.383439Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_sbi_instagram_posts.ibd' OS error: 103
2025-06-10T12:22:21.383824Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.384370Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.385065Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_sbi_instagram_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.386057Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_sbi_instagram_posts` because it could not be opened.
2025-06-10T12:22:21.386962Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.387257Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.387583Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.388167Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_sgpb_subscribers.ibd' OS error: 103
2025-06-10T12:22:21.388536Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.388854Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.389340Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_sgpb_subscribers`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.390067Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_sgpb_subscribers` because it could not be opened.
2025-06-10T12:22:21.390939Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.391224Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.391505Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.391955Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_sgpb_subscription_error_log.ibd' OS error: 103
2025-06-10T12:22:21.392346Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.392617Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.393150Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_sgpb_subscription_error_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.393818Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_sgpb_subscription_error_log` because it could not be opened.
2025-06-10T12:22:21.394385Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.394699Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.395041Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.395484Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:21.395886Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.396195Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.396617Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.397215Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:21.397642Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.397942Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.398213Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.398594Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:21.398961Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.399223Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.399634Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.400232Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:21.400625Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.400914Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.401407Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.401837Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:21.402177Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.402439Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.402882Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.403496Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_termmeta` because it could not be opened.
2025-06-10T12:22:21.404001Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.404269Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.404536Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.404970Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_terms.ibd' OS error: 103
2025-06-10T12:22:21.405284Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.405539Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.406021Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.406565Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_terms` because it could not be opened.
2025-06-10T12:22:21.406987Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.407428Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.407771Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.408247Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:21.408684Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.409087Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.409543Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.410138Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_usermeta` because it could not be opened.
2025-06-10T12:22:21.410539Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.411059Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.411342Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.411817Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_users.ibd' OS error: 103
2025-06-10T12:22:21.412144Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.412409Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.412894Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.413470Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_users` because it could not be opened.
2025-06-10T12:22:21.414016Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.414289Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.414561Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.415018Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_wc_admin_note_actions.ibd' OS error: 103
2025-06-10T12:22:21.415373Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.415705Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.416118Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_wc_admin_note_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.417135Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_wc_admin_note_actions` because it could not be opened.
2025-06-10T12:22:21.418108Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.418371Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.418854Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.419344Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_wc_admin_notes.ibd' OS error: 103
2025-06-10T12:22:21.419717Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.419993Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.420572Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_wc_admin_notes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.421130Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_wc_admin_notes` because it could not be opened.
2025-06-10T12:22:21.421638Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.421910Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.422181Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.422626Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_wc_category_lookup.ibd' OS error: 103
2025-06-10T12:22:21.422980Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.423305Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.423721Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_wc_category_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.424434Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_wc_category_lookup` because it could not be opened.
2025-06-10T12:22:21.424897Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.425164Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.425523Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.426003Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_wc_customer_lookup.ibd' OS error: 103
2025-06-10T12:22:21.426484Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.426791Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.427353Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_wc_customer_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.428036Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_wc_customer_lookup` because it could not be opened.
2025-06-10T12:22:21.428630Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.428913Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.429209Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.429690Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_wc_download_log.ibd' OS error: 103
2025-06-10T12:22:21.430053Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.430420Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.430889Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_wc_download_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.431768Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_wc_download_log` because it could not be opened.
2025-06-10T12:22:21.432408Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.432698Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.432963Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.433414Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_wc_order_coupon_lookup.ibd' OS error: 103
2025-06-10T12:22:21.433845Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.434113Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.434563Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_wc_order_coupon_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.435435Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_wc_order_coupon_lookup` because it could not be opened.
2025-06-10T12:22:21.435930Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.436257Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.436543Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.436930Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_wc_order_product_lookup.ibd' OS error: 103
2025-06-10T12:22:21.437354Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.437622Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.438020Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_wc_order_product_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.438668Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_wc_order_product_lookup` because it could not be opened.
2025-06-10T12:22:21.439098Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.439391Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.439664Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.440045Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_wc_order_stats.ibd' OS error: 103
2025-06-10T12:22:21.440417Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.440677Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.441353Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_wc_order_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.441934Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_wc_order_stats` because it could not be opened.
2025-06-10T12:22:21.442501Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.442878Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.443272Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.443663Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_wc_order_tax_lookup.ibd' OS error: 103
2025-06-10T12:22:21.444008Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.444347Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.444760Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_wc_order_tax_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.445484Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_wc_order_tax_lookup` because it could not be opened.
2025-06-10T12:22:21.446003Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.446370Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.446639Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.447006Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_wc_product_meta_lookup.ibd' OS error: 103
2025-06-10T12:22:21.447444Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.447901Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.448767Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_wc_product_meta_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.450059Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_wc_product_meta_lookup` because it could not be opened.
2025-06-10T12:22:21.450608Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.450940Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.451434Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.451956Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_wc_reserved_stock.ibd' OS error: 103
2025-06-10T12:22:21.452358Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.452617Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.453125Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_wc_reserved_stock`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.453745Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_wc_reserved_stock` because it could not be opened.
2025-06-10T12:22:21.454190Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.454461Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.454783Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.455196Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_wc_tax_rate_classes.ibd' OS error: 103
2025-06-10T12:22:21.455585Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.455888Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.456306Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_wc_tax_rate_classes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.456941Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_wc_tax_rate_classes` because it could not be opened.
2025-06-10T12:22:21.457420Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.457740Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.458059Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.458849Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_wc_webhooks.ibd' OS error: 103
2025-06-10T12:22:21.459277Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.459723Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.460160Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_wc_webhooks`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.460839Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_wc_webhooks` because it could not be opened.
2025-06-10T12:22:21.461338Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.461591Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.461904Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.462319Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_woocommerce_api_keys.ibd' OS error: 103
2025-06-10T12:22:21.462772Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.463097Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.463727Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_woocommerce_api_keys`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.464300Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_woocommerce_api_keys` because it could not be opened.
2025-06-10T12:22:21.464849Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.465141Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.465405Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.465819Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_woocommerce_attribute_taxonomies.ibd' OS error: 103
2025-06-10T12:22:21.466183Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.466462Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.466938Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_woocommerce_attribute_taxonomies`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.467560Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_woocommerce_attribute_taxonomies` because it could not be opened.
2025-06-10T12:22:21.468073Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.468327Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.468595Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.469053Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_woocommerce_downloadable_product_permissions.ibd' OS error: 103
2025-06-10T12:22:21.469443Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.469856Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.470268Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_woocommerce_downloadable_product_permissions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.470978Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_woocommerce_downloadable_product_permissions` because it could not be opened.
2025-06-10T12:22:21.471415Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.471746Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.472015Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.472375Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_woocommerce_log.ibd' OS error: 103
2025-06-10T12:22:21.472763Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.473015Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.473410Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_woocommerce_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.474202Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_woocommerce_log` because it could not be opened.
2025-06-10T12:22:21.474792Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.475047Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.475313Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.475771Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_woocommerce_order_itemmeta.ibd' OS error: 103
2025-06-10T12:22:21.476253Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.476524Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.476987Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_woocommerce_order_itemmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.477802Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_woocommerce_order_itemmeta` because it could not be opened.
2025-06-10T12:22:21.478307Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.478617Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.478894Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.479256Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_woocommerce_order_items.ibd' OS error: 103
2025-06-10T12:22:21.479650Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.479955Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.480406Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_woocommerce_order_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.481427Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_woocommerce_order_items` because it could not be opened.
2025-06-10T12:22:21.482769Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.483078Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.483427Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.483845Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_woocommerce_payment_tokenmeta.ibd' OS error: 103
2025-06-10T12:22:21.484320Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.484887Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.485459Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_woocommerce_payment_tokenmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.486082Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_woocommerce_payment_tokenmeta` because it could not be opened.
2025-06-10T12:22:21.486642Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.486905Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.487224Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.487727Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_woocommerce_payment_tokens.ibd' OS error: 103
2025-06-10T12:22:21.488118Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.488455Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.488890Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_woocommerce_payment_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.489582Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_woocommerce_payment_tokens` because it could not be opened.
2025-06-10T12:22:21.490069Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.490513Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.490799Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.491382Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_woocommerce_sessions.ibd' OS error: 103
2025-06-10T12:22:21.491859Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.492167Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.492607Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_woocommerce_sessions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.493259Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_woocommerce_sessions` because it could not be opened.
2025-06-10T12:22:21.493723Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.493991Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.494307Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.494692Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_woocommerce_shipping_zone_locations.ibd' OS error: 103
2025-06-10T12:22:21.495095Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.495381Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.495802Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_woocommerce_shipping_zone_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.496559Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_woocommerce_shipping_zone_locations` because it could not be opened.
2025-06-10T12:22:21.497044Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.497498Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.497782Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.498249Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_woocommerce_shipping_zone_methods.ibd' OS error: 103
2025-06-10T12:22:21.498768Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.499054Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.499567Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_woocommerce_shipping_zone_methods`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.500266Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_woocommerce_shipping_zone_methods` because it could not be opened.
2025-06-10T12:22:21.500721Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.501089Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.501438Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.501800Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_woocommerce_shipping_zones.ibd' OS error: 103
2025-06-10T12:22:21.502237Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.502509Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.502898Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_woocommerce_shipping_zones`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.503613Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_woocommerce_shipping_zones` because it could not be opened.
2025-06-10T12:22:21.504032Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.504422Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.504814Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.505299Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_woocommerce_tax_rate_locations.ibd' OS error: 103
2025-06-10T12:22:21.505709Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.505959Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.506528Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_woocommerce_tax_rate_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.507255Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_woocommerce_tax_rate_locations` because it could not be opened.
2025-06-10T12:22:21.507705Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.507958Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.508356Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.508734Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_woocommerce_tax_rates.ibd' OS error: 103
2025-06-10T12:22:21.509182Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.509458Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.509861Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_woocommerce_tax_rates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.510559Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_woocommerce_tax_rates` because it could not be opened.
2025-06-10T12:22:21.510977Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.511435Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.511704Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.512166Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_wpgmza.ibd' OS error: 103
2025-06-10T12:22:21.513401Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.514101Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.515859Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_wpgmza`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.516599Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_wpgmza` because it could not be opened.
2025-06-10T12:22:21.517069Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.517420Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.517686Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.518117Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_wpgmza_circles.ibd' OS error: 103
2025-06-10T12:22:21.518463Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.518715Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.519208Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_wpgmza_circles`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.519793Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_wpgmza_circles` because it could not be opened.
2025-06-10T12:22:21.520548Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.520894Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.521295Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.521688Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_wpgmza_maps.ibd' OS error: 103
2025-06-10T12:22:21.522106Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.522390Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.522822Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_wpgmza_maps`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.523496Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_wpgmza_maps` because it could not be opened.
2025-06-10T12:22:21.524107Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.524395Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.524667Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.525100Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_wpgmza_polygon.ibd' OS error: 103
2025-06-10T12:22:21.525481Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.525742Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.526315Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_wpgmza_polygon`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.526895Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_wpgmza_polygon` because it could not be opened.
2025-06-10T12:22:21.527403Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.527677Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.527937Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.528418Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_wpgmza_polylines.ibd' OS error: 103
2025-06-10T12:22:21.528748Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.529065Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.529627Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_wpgmza_polylines`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.530350Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_wpgmza_polylines` because it could not be opened.
2025-06-10T12:22:21.530768Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.531119Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.531526Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.531905Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_wpgmza_rectangles.ibd' OS error: 103
2025-06-10T12:22:21.532308Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.532565Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.532978Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_wpgmza_rectangles`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.533777Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_wpgmza_rectangles` because it could not be opened.
2025-06-10T12:22:21.534344Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.534618Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.534887Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.535343Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_wpie_template.ibd' OS error: 103
2025-06-10T12:22:21.535671Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.535923Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.536394Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_wpie_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.536948Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_wpie_template` because it could not be opened.
2025-06-10T12:22:21.537442Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.537695Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.538012Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.538416Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:21.538784Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.539135Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.539548Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.540242Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:21.540747Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.541139Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.541436Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.541826Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:21.542371Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.542629Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.543080Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.543639Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:21.544218Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.545322Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.546286Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.546775Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:21.547542Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.547858Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.548377Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.549017Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:21.549457Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.549731Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.550102Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.550536Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem19\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:21.550962Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.551242Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.551669Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem19/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.552384Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem19/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:21.552917Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.553238Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.553514Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.553983Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1hr\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:21.554343Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.554618Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.555118Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1hr/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.555713Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1hr/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:21.556522Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.556789Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.557127Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.557514Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1hr\wp_comments.ibd' OS error: 103
2025-06-10T12:22:21.557866Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.558179Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.558582Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1hr/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.559235Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1hr/wp_comments` because it could not be opened.
2025-06-10T12:22:21.559901Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.560216Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.560503Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.561151Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1hr\wp_links.ibd' OS error: 103
2025-06-10T12:22:21.561512Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.561785Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.562251Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1hr/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.562801Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1hr/wp_links` because it could not be opened.
2025-06-10T12:22:21.563437Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.563717Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.564030Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.564419Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1hr\wp_options.ibd' OS error: 103
2025-06-10T12:22:21.564756Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.565122Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.565543Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1hr/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.566188Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1hr/wp_options` because it could not be opened.
2025-06-10T12:22:21.566576Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.566876Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.567203Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.567659Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1hr\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:21.568074Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.568336Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.568733Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1hr/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.569350Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1hr/wp_postmeta` because it could not be opened.
2025-06-10T12:22:21.569738Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.570075Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.570349Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.570734Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1hr\wp_posts.ibd' OS error: 103
2025-06-10T12:22:21.571105Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.571374Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.571805Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1hr/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.572560Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1hr/wp_posts` because it could not be opened.
2025-06-10T12:22:21.573139Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.573401Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.573672Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.574287Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1hr\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:21.574691Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.575009Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.575495Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1hr/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.577016Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1hr/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:21.577611Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.577878Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.578258Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.578689Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1hr\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:21.579218Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.579492Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.579941Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1hr/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.580542Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1hr/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:21.580999Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.581292Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.581938Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.582531Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1hr\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:21.583013Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.583357Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.584052Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1hr/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.585187Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1hr/wp_termmeta` because it could not be opened.
2025-06-10T12:22:21.585772Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.586070Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.586352Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.586798Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1hr\wp_terms.ibd' OS error: 103
2025-06-10T12:22:21.587159Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.587453Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.587942Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1hr/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.589321Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1hr/wp_terms` because it could not be opened.
2025-06-10T12:22:21.589894Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.590220Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.590589Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.591618Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1hr\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:21.592185Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.592536Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.593045Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1hr/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.593624Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1hr/wp_usermeta` because it could not be opened.
2025-06-10T12:22:21.594267Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.594544Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.594838Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.595251Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem1hr\wp_users.ibd' OS error: 103
2025-06-10T12:22:21.595673Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.595950Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.596360Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem1hr/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.596982Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem1hr/wp_users` because it could not be opened.
2025-06-10T12:22:21.597382Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.597699Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.597986Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.598360Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem2\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:21.598813Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.599134Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.599580Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem2/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.600332Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem2/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:21.600786Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.601039Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.601365Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.601915Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem2\wp_comments.ibd' OS error: 103
2025-06-10T12:22:21.602379Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.602884Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.603541Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem2/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.604292Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem2/wp_comments` because it could not be opened.
2025-06-10T12:22:21.605251Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.605561Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.606130Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.606577Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem2\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:21.606936Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.607233Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.607772Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem2/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.608324Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem2/wp_fbv` because it could not be opened.
2025-06-10T12:22:21.608812Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.609070Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.609330Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.609783Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem2\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:21.610346Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.610613Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.611118Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem2/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.611799Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem2/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:21.612748Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.613201Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.613475Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.613848Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem2\wp_gg_attributes.ibd' OS error: 103
2025-06-10T12:22:21.614297Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.614550Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.614955Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem2/wp_gg_attributes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.615642Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem2/wp_gg_attributes` because it could not be opened.
2025-06-10T12:22:21.616115Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.616388Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.616663Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.617116Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem2\wp_gg_cdn.ibd' OS error: 103
2025-06-10T12:22:21.617643Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.618101Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.618694Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem2/wp_gg_cdn`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.619903Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem2/wp_gg_cdn` because it could not be opened.
2025-06-10T12:22:21.620703Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.621214Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.621650Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.622196Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem2\wp_gg_folders.ibd' OS error: 103
2025-06-10T12:22:21.622731Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.623135Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.623735Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem2/wp_gg_folders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.624584Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem2/wp_gg_folders` because it could not be opened.
2025-06-10T12:22:21.625312Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.625600Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.626055Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.626816Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem2\wp_gg_galleries.ibd' OS error: 103
2025-06-10T12:22:21.627507Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.628102Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.628689Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem2/wp_gg_galleries`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.629609Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem2/wp_gg_galleries` because it could not be opened.
2025-06-10T12:22:21.630172Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.630460Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.630747Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.631218Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem2\wp_gg_galleries_excluded.ibd' OS error: 103
2025-06-10T12:22:21.631606Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.631992Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.632482Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem2/wp_gg_galleries_excluded`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.633144Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem2/wp_gg_galleries_excluded` because it could not be opened.
2025-06-10T12:22:21.633614Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.633883Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.634191Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.634916Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem2\wp_gg_galleries_resources.ibd' OS error: 103
2025-06-10T12:22:21.635736Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.636125Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.636563Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem2/wp_gg_galleries_resources`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.637202Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem2/wp_gg_galleries_resources` because it could not be opened.
2025-06-10T12:22:21.637676Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.637961Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.638258Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.638645Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem2\wp_gg_image_optimize.ibd' OS error: 103
2025-06-10T12:22:21.639026Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.639295Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.639713Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem2/wp_gg_image_optimize`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.640347Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem2/wp_gg_image_optimize` because it could not be opened.
2025-06-10T12:22:21.640786Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.641099Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.641374Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.641811Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem2\wp_gg_membership_presets.ibd' OS error: 103
2025-06-10T12:22:21.642231Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.642503Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.643018Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem2/wp_gg_membership_presets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.643613Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem2/wp_gg_membership_presets` because it could not be opened.
2025-06-10T12:22:21.644091Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.644364Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.644636Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.645093Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem2\wp_gg_photos.ibd' OS error: 103
2025-06-10T12:22:21.645422Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.645682Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.646218Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem2/wp_gg_photos`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.646777Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem2/wp_gg_photos` because it could not be opened.
2025-06-10T12:22:21.647351Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.647622Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.647955Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.648378Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem2\wp_gg_photos_pos.ibd' OS error: 103
2025-06-10T12:22:21.648713Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.649011Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.649430Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem2/wp_gg_photos_pos`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.650106Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem2/wp_gg_photos_pos` because it could not be opened.
2025-06-10T12:22:21.650529Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.650878Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.651220Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.651760Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem2\wp_gg_photos_settings.ibd' OS error: 103
2025-06-10T12:22:21.652158Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.652714Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.653195Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem2/wp_gg_photos_settings`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.653794Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem2/wp_gg_photos_settings` because it could not be opened.
2025-06-10T12:22:21.654346Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.654657Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.655016Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.655501Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem2\wp_gg_settings_presets.ibd' OS error: 103
2025-06-10T12:22:21.655852Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.656212Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.656666Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem2/wp_gg_settings_presets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.657333Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem2/wp_gg_settings_presets` because it could not be opened.
2025-06-10T12:22:21.657805Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.658417Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.659086Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.659594Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem2\wp_gg_settings_sets.ibd' OS error: 103
2025-06-10T12:22:21.659953Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.660429Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.661462Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem2/wp_gg_settings_sets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.662376Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem2/wp_gg_settings_sets` because it could not be opened.
2025-06-10T12:22:21.663234Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.663643Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.664126Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.664808Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem2\wp_gg_stats.ibd' OS error: 103
2025-06-10T12:22:21.665366Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.665854Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.666375Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem2/wp_gg_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.667289Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem2/wp_gg_stats` because it could not be opened.
2025-06-10T12:22:21.667904Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.668183Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.668460Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.668940Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem2\wp_gg_tags.ibd' OS error: 103
2025-06-10T12:22:21.669288Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.669735Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.670205Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem2/wp_gg_tags`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.670915Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem2/wp_gg_tags` because it could not be opened.
2025-06-10T12:22:21.671401Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.671730Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.672017Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.672410Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem2\wp_links.ibd' OS error: 103
2025-06-10T12:22:21.672782Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.673080Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.673558Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem2/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.674209Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem2/wp_links` because it could not be opened.
2025-06-10T12:22:21.674674Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.675004Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.675294Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.675725Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem2\wp_newsletter.ibd' OS error: 103
2025-06-10T12:22:21.676103Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.676371Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.677177Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem2/wp_newsletter`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.677846Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem2/wp_newsletter` because it could not be opened.
2025-06-10T12:22:21.678455Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.678840Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.679135Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.679509Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem2\wp_newsletter_emails.ibd' OS error: 103
2025-06-10T12:22:21.679934Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.680216Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.680613Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem2/wp_newsletter_emails`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.681265Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem2/wp_newsletter_emails` because it could not be opened.
2025-06-10T12:22:21.681778Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.682093Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.682433Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.683004Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem2\wp_newsletter_sent.ibd' OS error: 103
2025-06-10T12:22:21.683423Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.683754Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.684182Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem2/wp_newsletter_sent`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.684860Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem2/wp_newsletter_sent` because it could not be opened.
2025-06-10T12:22:21.685304Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.685575Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.685950Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.686353Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem2\wp_newsletter_stats.ibd' OS error: 103
2025-06-10T12:22:21.686818Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.687107Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.687566Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem2/wp_newsletter_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.688255Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem2/wp_newsletter_stats` because it could not be opened.
2025-06-10T12:22:21.688746Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.689052Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.689307Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.689905Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem2\wp_newsletter_user_logs.ibd' OS error: 103
2025-06-10T12:22:21.690537Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.690790Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.691408Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem2/wp_newsletter_user_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.692545Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem2/wp_newsletter_user_logs` because it could not be opened.
2025-06-10T12:22:21.693563Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.693852Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.694131Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.694547Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem2\wp_options.ibd' OS error: 103
2025-06-10T12:22:21.694946Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.695269Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.695855Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem2/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.696490Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem2/wp_options` because it could not be opened.
2025-06-10T12:22:21.696920Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.697186Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.697460Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.697949Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem2\wp_post_views.ibd' OS error: 103
2025-06-10T12:22:21.698267Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.698569Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.699017Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem2/wp_post_views`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.700264Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem2/wp_post_views` because it could not be opened.
2025-06-10T12:22:21.700967Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.701244Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.701569Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.701976Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem2\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:21.702320Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.702662Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.703114Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem2/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.703790Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem2/wp_postmeta` because it could not be opened.
2025-06-10T12:22:21.704264Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.704582Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.704905Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.705270Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem2\wp_posts.ibd' OS error: 103
2025-06-10T12:22:21.705659Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.705984Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.706394Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem2/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.707367Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem2/wp_posts` because it could not be opened.
2025-06-10T12:22:21.707936Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.708201Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.708499Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.708890Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem2\wp_revslider_css.ibd' OS error: 103
2025-06-10T12:22:21.709212Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.709547Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.709969Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem2/wp_revslider_css`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.710627Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem2/wp_revslider_css` because it could not be opened.
2025-06-10T12:22:21.711019Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.711271Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.711624Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.712015Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem2\wp_revslider_css_bkp.ibd' OS error: 103
2025-06-10T12:22:21.712350Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.712730Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.713480Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem2/wp_revslider_css_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.714094Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem2/wp_revslider_css_bkp` because it could not be opened.
2025-06-10T12:22:21.714573Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.714847Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.715106Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.715716Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem2\wp_revslider_layer_animations.ibd' OS error: 103
2025-06-10T12:22:21.716400Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.716978Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.717576Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem2/wp_revslider_layer_animations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.718227Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem2/wp_revslider_layer_animations` because it could not be opened.
2025-06-10T12:22:21.718759Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.719017Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.719276Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.719733Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem2\wp_revslider_layer_animations_bkp.ibd' OS error: 103
2025-06-10T12:22:21.720089Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.720444Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.721131Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem2/wp_revslider_layer_animations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.723153Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem2/wp_revslider_layer_animations_bkp` because it could not be opened.
2025-06-10T12:22:21.723768Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.724077Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.724359Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.724751Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem2\wp_revslider_navigations.ibd' OS error: 103
2025-06-10T12:22:21.725146Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.725415Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.725860Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem2/wp_revslider_navigations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.726478Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem2/wp_revslider_navigations` because it could not be opened.
2025-06-10T12:22:21.726949Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.727229Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.727560Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.728120Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem2\wp_revslider_navigations_bkp.ibd' OS error: 103
2025-06-10T12:22:21.728668Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.729035Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.729506Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem2/wp_revslider_navigations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.730273Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem2/wp_revslider_navigations_bkp` because it could not be opened.
2025-06-10T12:22:21.730802Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.731177Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.731442Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.731810Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem2\wp_revslider_sliders.ibd' OS error: 103
2025-06-10T12:22:21.732307Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.732558Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.733012Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem2/wp_revslider_sliders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.733563Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem2/wp_revslider_sliders` because it could not be opened.
2025-06-10T12:22:21.734041Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.734366Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.734636Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.735254Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem2\wp_revslider_sliders_bkp.ibd' OS error: 103
2025-06-10T12:22:21.735648Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.735964Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.736384Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem2/wp_revslider_sliders_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.737020Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem2/wp_revslider_sliders_bkp` because it could not be opened.
2025-06-10T12:22:21.737441Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.737710Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.738016Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.738398Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem2\wp_revslider_slides.ibd' OS error: 103
2025-06-10T12:22:21.738751Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.739055Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.739468Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem2/wp_revslider_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.740090Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem2/wp_revslider_slides` because it could not be opened.
2025-06-10T12:22:21.740480Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.740829Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.741128Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.741514Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem2\wp_revslider_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:21.741905Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.742245Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.742643Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem2/wp_revslider_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.743424Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem2/wp_revslider_slides_bkp` because it could not be opened.
2025-06-10T12:22:21.743863Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.744136Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.744397Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.744763Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem2\wp_revslider_static_slides.ibd' OS error: 103
2025-06-10T12:22:21.745301Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.745555Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.746060Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem2/wp_revslider_static_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.746671Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem2/wp_revslider_static_slides` because it could not be opened.
2025-06-10T12:22:21.747253Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.747534Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.747929Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.748388Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem2\wp_revslider_static_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:21.748755Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.749152Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.749664Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem2/wp_revslider_static_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.750356Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem2/wp_revslider_static_slides_bkp` because it could not be opened.
2025-06-10T12:22:21.750837Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.751120Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.751394Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.751800Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem2\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:21.752236Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.752497Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.752957Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem2/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.753517Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem2/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:21.754138Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.754406Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.754665Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.755126Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem2\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:21.755445Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.755693Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.756221Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem2/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.756820Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem2/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:21.757241Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.757647Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.758032Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.758391Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem2\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:21.758699Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.759116Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.759498Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem2/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.760197Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem2/wp_termmeta` because it could not be opened.
2025-06-10T12:22:21.760588Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.760954Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.761436Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.761887Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem2\wp_terms.ibd' OS error: 103
2025-06-10T12:22:21.762268Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.762570Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.763085Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem2/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.763684Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem2/wp_terms` because it could not be opened.
2025-06-10T12:22:21.764180Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.764439Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.764703Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.765238Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem2\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:21.765580Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.765923Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.766365Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem2/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.767199Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem2/wp_usermeta` because it could not be opened.
2025-06-10T12:22:21.767596Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.768368Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.769401Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.770453Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem2\wp_users.ibd' OS error: 103
2025-06-10T12:22:21.770865Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.771130Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.771618Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem2/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.772244Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem2/wp_users` because it could not be opened.
2025-06-10T12:22:21.772673Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.772978Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.773259Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.773644Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem2\wp_wpfm_backup.ibd' OS error: 103
2025-06-10T12:22:21.774035Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.774293Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.774719Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem2/wp_wpfm_backup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.775367Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem2/wp_wpfm_backup` because it could not be opened.
2025-06-10T12:22:21.775882Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.776171Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.776437Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.776876Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem2\wp_yoast_seo_links.ibd' OS error: 103
2025-06-10T12:22:21.777232Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.777509Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.778019Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem2/wp_yoast_seo_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.778612Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem2/wp_yoast_seo_links` because it could not be opened.
2025-06-10T12:22:21.779152Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.779470Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.779790Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.780332Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem2\wp_yoast_seo_meta.ibd' OS error: 103
2025-06-10T12:22:21.780741Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.781019Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.781443Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem2/wp_yoast_seo_meta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.782060Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem2/wp_yoast_seo_meta` because it could not be opened.
2025-06-10T12:22:21.782483Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.782783Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.783055Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.783442Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem20\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:21.783809Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.784070Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.784489Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem20/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.785091Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem20/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:21.785475Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.785775Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.786048Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.786434Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem20\wp_comments.ibd' OS error: 103
2025-06-10T12:22:21.786795Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.787068Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.787487Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem20/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.788103Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem20/wp_comments` because it could not be opened.
2025-06-10T12:22:21.788483Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.788777Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.789049Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.789428Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem20\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:21.789800Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.790087Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.790514Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem20/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.791111Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem20/wp_fbv` because it could not be opened.
2025-06-10T12:22:21.791507Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.791809Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.792084Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.792472Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem20\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:21.792852Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.793116Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.793536Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem20/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.794213Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem20/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:21.794638Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.794941Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.795219Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.795606Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem20\wp_gg_attributes.ibd' OS error: 103
2025-06-10T12:22:21.795979Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.796248Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.796723Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem20/wp_gg_attributes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.797428Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem20/wp_gg_attributes` because it could not be opened.
2025-06-10T12:22:21.797955Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.798294Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.798577Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.799050Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem20\wp_gg_cdn.ibd' OS error: 103
2025-06-10T12:22:21.799371Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.799880Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.801490Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem20/wp_gg_cdn`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.803047Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem20/wp_gg_cdn` because it could not be opened.
2025-06-10T12:22:21.803515Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.803825Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.804108Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.804496Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem20\wp_gg_folders.ibd' OS error: 103
2025-06-10T12:22:21.804856Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.805121Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.805545Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem20/wp_gg_folders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.806189Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem20/wp_gg_folders` because it could not be opened.
2025-06-10T12:22:21.806658Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.806944Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.807229Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.807665Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem20\wp_gg_galleries.ibd' OS error: 103
2025-06-10T12:22:21.808049Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.808320Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.808804Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem20/wp_gg_galleries`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.809660Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem20/wp_gg_galleries` because it could not be opened.
2025-06-10T12:22:21.810255Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.810537Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.810836Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.811224Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem20\wp_gg_galleries_excluded.ibd' OS error: 103
2025-06-10T12:22:21.811588Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.811898Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.812326Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem20/wp_gg_galleries_excluded`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.812944Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem20/wp_gg_galleries_excluded` because it could not be opened.
2025-06-10T12:22:21.813363Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.813668Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.813966Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.814372Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem20\wp_gg_galleries_resources.ibd' OS error: 103
2025-06-10T12:22:21.814754Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.815024Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.815441Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem20/wp_gg_galleries_resources`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.816086Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem20/wp_gg_galleries_resources` because it could not be opened.
2025-06-10T12:22:21.816495Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.816783Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.817057Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.817447Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem20\wp_gg_image_optimize.ibd' OS error: 103
2025-06-10T12:22:21.817826Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.818091Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.818505Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem20/wp_gg_image_optimize`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.819123Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem20/wp_gg_image_optimize` because it could not be opened.
2025-06-10T12:22:21.819515Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.819811Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.820085Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.820474Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem20\wp_gg_membership_presets.ibd' OS error: 103
2025-06-10T12:22:21.820867Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.821134Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.821547Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem20/wp_gg_membership_presets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.822195Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem20/wp_gg_membership_presets` because it could not be opened.
2025-06-10T12:22:21.822613Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.823070Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.823352Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.823796Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem20\wp_gg_photos.ibd' OS error: 103
2025-06-10T12:22:21.824135Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.824401Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.824835Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem20/wp_gg_photos`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.825414Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem20/wp_gg_photos` because it could not be opened.
2025-06-10T12:22:21.825874Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.826157Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.826440Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.826851Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem20\wp_gg_photos_pos.ibd' OS error: 103
2025-06-10T12:22:21.827202Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.827468Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.827941Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem20/wp_gg_photos_pos`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.828603Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem20/wp_gg_photos_pos` because it could not be opened.
2025-06-10T12:22:21.829065Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.829325Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.829643Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.830032Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem20\wp_gg_photos_settings.ibd' OS error: 103
2025-06-10T12:22:21.830373Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.830719Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.831121Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem20/wp_gg_photos_settings`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.831774Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem20/wp_gg_photos_settings` because it could not be opened.
2025-06-10T12:22:21.832617Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.833004Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.833284Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.833731Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem20\wp_gg_settings_presets.ibd' OS error: 103
2025-06-10T12:22:21.834294Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.834560Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.835084Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem20/wp_gg_settings_presets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.835755Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem20/wp_gg_settings_presets` because it could not be opened.
2025-06-10T12:22:21.836220Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.836518Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.836781Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.837151Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem20\wp_gg_settings_sets.ibd' OS error: 103
2025-06-10T12:22:21.837584Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.837868Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.838373Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem20/wp_gg_settings_sets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.838986Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem20/wp_gg_settings_sets` because it could not be opened.
2025-06-10T12:22:21.839500Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.839762Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.840028Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.840484Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem20\wp_gg_stats.ibd' OS error: 103
2025-06-10T12:22:21.840937Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.841325Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.841901Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem20/wp_gg_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.842629Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem20/wp_gg_stats` because it could not be opened.
2025-06-10T12:22:21.843047Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.843421Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.843761Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.844131Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem20\wp_gg_tags.ibd' OS error: 103
2025-06-10T12:22:21.844593Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.844893Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.845352Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem20/wp_gg_tags`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.845889Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem20/wp_gg_tags` because it could not be opened.
2025-06-10T12:22:21.846342Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.846611Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.846918Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.847400Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem20\wp_links.ibd' OS error: 103
2025-06-10T12:22:21.847725Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.847978Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.848492Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem20/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.849192Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem20/wp_links` because it could not be opened.
2025-06-10T12:22:21.849620Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.849895Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.850210Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.850599Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem20\wp_newsletter.ibd' OS error: 103
2025-06-10T12:22:21.850935Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.851245Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.851664Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem20/wp_newsletter`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.852275Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem20/wp_newsletter` because it could not be opened.
2025-06-10T12:22:21.852655Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.852919Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.853233Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.853619Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem20\wp_newsletter_emails.ibd' OS error: 103
2025-06-10T12:22:21.854053Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.854389Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.854981Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem20/wp_newsletter_emails`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.855639Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem20/wp_newsletter_emails` because it could not be opened.
2025-06-10T12:22:21.856048Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.856354Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.856622Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.857005Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem20\wp_newsletter_sent.ibd' OS error: 103
2025-06-10T12:22:21.857454Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.857716Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.858158Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem20/wp_newsletter_sent`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.858828Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem20/wp_newsletter_sent` because it could not be opened.
2025-06-10T12:22:21.859301Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.859570Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.859840Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.860263Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem20\wp_newsletter_stats.ibd' OS error: 103
2025-06-10T12:22:21.860770Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.861086Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.861609Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem20/wp_newsletter_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.862368Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem20/wp_newsletter_stats` because it could not be opened.
2025-06-10T12:22:21.862776Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.863027Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.863404Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.863763Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem20\wp_newsletter_user_logs.ibd' OS error: 103
2025-06-10T12:22:21.864249Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.864821Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.865311Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem20/wp_newsletter_user_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.866068Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem20/wp_newsletter_user_logs` because it could not be opened.
2025-06-10T12:22:21.866512Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.867177Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.867497Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.867898Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem20\wp_options.ibd' OS error: 103
2025-06-10T12:22:21.868288Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.868552Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.868968Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem20/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.869588Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem20/wp_options` because it could not be opened.
2025-06-10T12:22:21.870050Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.870323Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.870600Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.871131Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem20\wp_post_views.ibd' OS error: 103
2025-06-10T12:22:21.871473Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.871737Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.872344Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem20/wp_post_views`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.872983Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem20/wp_post_views` because it could not be opened.
2025-06-10T12:22:21.873817Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.874179Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.874469Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.874863Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem20\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:21.875246Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.875514Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.875933Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem20/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.876637Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem20/wp_postmeta` because it could not be opened.
2025-06-10T12:22:21.877093Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.877369Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.877649Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.878091Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem20\wp_posts.ibd' OS error: 103
2025-06-10T12:22:21.878424Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.878690Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.879181Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem20/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.879772Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem20/wp_posts` because it could not be opened.
2025-06-10T12:22:21.880210Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.880668Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.881025Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.881422Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem20\wp_revslider_css.ibd' OS error: 103
2025-06-10T12:22:21.881762Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.882105Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.882542Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem20/wp_revslider_css`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.883246Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem20/wp_revslider_css` because it could not be opened.
2025-06-10T12:22:21.883656Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.883924Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.884257Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.884643Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem20\wp_revslider_css_bkp.ibd' OS error: 103
2025-06-10T12:22:21.885049Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.885314Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.885726Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem20/wp_revslider_css_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.886375Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem20/wp_revslider_css_bkp` because it could not be opened.
2025-06-10T12:22:21.887005Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.887486Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.887753Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.888203Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem20\wp_revslider_layer_animations.ibd' OS error: 103
2025-06-10T12:22:21.888591Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.888847Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.889317Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem20/wp_revslider_layer_animations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.889975Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem20/wp_revslider_layer_animations` because it could not be opened.
2025-06-10T12:22:21.890473Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.890744Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.891052Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.891441Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem20\wp_revslider_layer_animations_bkp.ibd' OS error: 103
2025-06-10T12:22:21.891822Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.892144Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.892568Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem20/wp_revslider_layer_animations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.893440Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem20/wp_revslider_layer_animations_bkp` because it could not be opened.
2025-06-10T12:22:21.893896Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.894333Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.894702Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.895183Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem20\wp_revslider_navigations.ibd' OS error: 103
2025-06-10T12:22:21.895527Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.896040Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.897654Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem20/wp_revslider_navigations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.898887Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem20/wp_revslider_navigations` because it could not be opened.
2025-06-10T12:22:21.899523Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.899804Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.900097Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.900512Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem20\wp_revslider_navigations_bkp.ibd' OS error: 103
2025-06-10T12:22:21.900880Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.901144Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.901625Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem20/wp_revslider_navigations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.902197Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem20/wp_revslider_navigations_bkp` because it could not be opened.
2025-06-10T12:22:21.902895Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.903173Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.903535Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.903938Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem20\wp_revslider_sliders.ibd' OS error: 103
2025-06-10T12:22:21.904286Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.904658Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.905095Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem20/wp_revslider_sliders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.905925Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem20/wp_revslider_sliders` because it could not be opened.
2025-06-10T12:22:21.906542Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.906822Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.907180Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.907654Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem20\wp_revslider_sliders_bkp.ibd' OS error: 103
2025-06-10T12:22:21.907995Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.908244Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.909022Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem20/wp_revslider_sliders_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.909703Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem20/wp_revslider_sliders_bkp` because it could not be opened.
2025-06-10T12:22:21.910145Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.910460Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.910734Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.911119Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem20\wp_revslider_slides.ibd' OS error: 103
2025-06-10T12:22:21.911511Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.911776Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.912190Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem20/wp_revslider_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.912814Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem20/wp_revslider_slides` because it could not be opened.
2025-06-10T12:22:21.913212Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.913549Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.913824Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.914208Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem20\wp_revslider_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:21.914601Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.914864Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.915278Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem20/wp_revslider_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.915956Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem20/wp_revslider_slides_bkp` because it could not be opened.
2025-06-10T12:22:21.916438Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.916714Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.917062Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.917517Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem20\wp_revslider_static_slides.ibd' OS error: 103
2025-06-10T12:22:21.917884Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.918148Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.918612Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem20/wp_revslider_static_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.919225Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem20/wp_revslider_static_slides` because it could not be opened.
2025-06-10T12:22:21.919743Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.920015Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.920315Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.920747Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem20\wp_revslider_static_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:21.921319Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.921641Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.922064Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem20/wp_revslider_static_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.922757Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem20/wp_revslider_static_slides_bkp` because it could not be opened.
2025-06-10T12:22:21.923290Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.923617Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.923873Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.924237Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem20\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:21.924632Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.924883Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.925306Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem20/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.925969Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem20/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:21.926498Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.926766Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.927023Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.927468Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem20\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:21.927859Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.928159Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.928873Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem20/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.929566Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem20/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:21.930111Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.930443Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.930863Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.931432Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem20\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:21.931843Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.932126Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.932630Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem20/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.933203Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem20/wp_termmeta` because it could not be opened.
2025-06-10T12:22:21.933686Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.933952Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.934222Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.934692Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem20\wp_terms.ibd' OS error: 103
2025-06-10T12:22:21.935049Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.935307Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.935782Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem20/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.936331Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem20/wp_terms` because it could not be opened.
2025-06-10T12:22:21.936874Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.937130Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.937444Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.937846Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem20\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:21.938254Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.938554Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.939208Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem20/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.939929Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem20/wp_usermeta` because it could not be opened.
2025-06-10T12:22:21.940460Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.940784Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.941059Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.941787Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem20\wp_users.ibd' OS error: 103
2025-06-10T12:22:21.942177Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.942493Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.942954Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem20/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.943690Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem20/wp_users` because it could not be opened.
2025-06-10T12:22:21.944132Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.944499Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.944776Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.945147Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem20\wp_wpfm_backup.ibd' OS error: 103
2025-06-10T12:22:21.945588Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.945836Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.946248Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem20/wp_wpfm_backup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.946882Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem20/wp_wpfm_backup` because it could not be opened.
2025-06-10T12:22:21.947260Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.947630Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.947934Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.948302Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem20\wp_yoast_seo_links.ibd' OS error: 103
2025-06-10T12:22:21.948785Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.949037Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.949500Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem20/wp_yoast_seo_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.950167Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem20/wp_yoast_seo_links` because it could not be opened.
2025-06-10T12:22:21.950822Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.951115Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.951567Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.952060Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem20\wp_yoast_seo_meta.ibd' OS error: 103
2025-06-10T12:22:21.952461Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.952727Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.953219Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem20/wp_yoast_seo_meta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.954037Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem20/wp_yoast_seo_meta` because it could not be opened.
2025-06-10T12:22:21.954656Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.954974Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.955274Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.955683Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:21.956022Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.956318Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.956778Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.957418Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:21.957930Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.958216Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.958530Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.958958Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_comments.ibd' OS error: 103
2025-06-10T12:22:21.959330Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.959609Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.960010Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.960646Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_comments` because it could not be opened.
2025-06-10T12:22:21.961031Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.961371Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.961922Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.962468Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:21.963753Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.964035Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.964536Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.965141Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_fbv` because it could not be opened.
2025-06-10T12:22:21.965613Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.965925Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.966234Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.966624Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:21.966987Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.967342Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.967763Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.968428Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:21.968876Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.969371Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.969658Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.970113Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_gg_attributes.ibd' OS error: 103
2025-06-10T12:22:21.970498Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.970766Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.971245Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_gg_attributes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.971849Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_gg_attributes` because it could not be opened.
2025-06-10T12:22:21.972415Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.972693Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.972969Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.973430Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_gg_cdn.ibd' OS error: 103
2025-06-10T12:22:21.973759Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.974019Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.974484Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_gg_cdn`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.975097Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_gg_cdn` because it could not be opened.
2025-06-10T12:22:21.975481Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.975748Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.976021Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.976455Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_gg_folders.ibd' OS error: 103
2025-06-10T12:22:21.976791Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.977104Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.977524Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_gg_folders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.978158Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_gg_folders` because it could not be opened.
2025-06-10T12:22:21.978536Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.978801Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.979147Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.979531Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_gg_galleries.ibd' OS error: 103
2025-06-10T12:22:21.979871Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.980182Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.980628Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_gg_galleries`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.981265Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_gg_galleries` because it could not be opened.
2025-06-10T12:22:21.981673Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.982009Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.982326Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.982721Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_gg_galleries_excluded.ibd' OS error: 103
2025-06-10T12:22:21.983131Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.983400Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.983926Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_gg_galleries_excluded`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.984545Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_gg_galleries_excluded` because it could not be opened.
2025-06-10T12:22:21.984964Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.985296Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.985572Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.985958Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_gg_galleries_resources.ibd' OS error: 103
2025-06-10T12:22:21.986380Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.986716Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.987187Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_gg_galleries_resources`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.987939Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_gg_galleries_resources` because it could not be opened.
2025-06-10T12:22:21.988589Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.988901Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.989212Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.989600Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_gg_image_optimize.ibd' OS error: 103
2025-06-10T12:22:21.989949Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.990276Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.990717Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_gg_image_optimize`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.991355Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_gg_image_optimize` because it could not be opened.
2025-06-10T12:22:21.991796Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.992159Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.992781Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.993307Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_gg_membership_presets.ibd' OS error: 103
2025-06-10T12:22:21.994070Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.994353Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:21.995377Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_gg_membership_presets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:21.996332Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_gg_membership_presets` because it could not be opened.
2025-06-10T12:22:21.997017Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:21.997462Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:21.997887Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:21.998484Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_gg_photos.ibd' OS error: 103
2025-06-10T12:22:21.998980Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:21.999370Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.000091Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_gg_photos`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.001049Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_gg_photos` because it could not be opened.
2025-06-10T12:22:22.001604Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.001895Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.002177Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.002621Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_gg_photos_pos.ibd' OS error: 103
2025-06-10T12:22:22.002992Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.003260Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.003695Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_gg_photos_pos`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.004278Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_gg_photos_pos` because it could not be opened.
2025-06-10T12:22:22.004737Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.005005Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.005300Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.005733Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_gg_photos_settings.ibd' OS error: 103
2025-06-10T12:22:22.006075Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.006356Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.006824Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_gg_photos_settings`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.007442Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_gg_photos_settings` because it could not be opened.
2025-06-10T12:22:22.007853Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.008118Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.008424Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.008817Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_gg_settings_presets.ibd' OS error: 103
2025-06-10T12:22:22.009169Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.009462Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.009880Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_gg_settings_presets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.010511Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_gg_settings_presets` because it could not be opened.
2025-06-10T12:22:22.010890Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.011268Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.011630Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.011997Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_gg_settings_sets.ibd' OS error: 103
2025-06-10T12:22:22.012326Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.012755Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.013141Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_gg_settings_sets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.013820Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_gg_settings_sets` because it could not be opened.
2025-06-10T12:22:22.014216Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.014636Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.014919Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.015316Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_gg_stats.ibd' OS error: 103
2025-06-10T12:22:22.015700Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.015959Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.016403Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_gg_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.016963Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_gg_stats` because it could not be opened.
2025-06-10T12:22:22.017324Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.017793Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.018061Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.018502Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_gg_tags.ibd' OS error: 103
2025-06-10T12:22:22.018835Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.019083Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.019736Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_gg_tags`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.020380Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_gg_tags` because it could not be opened.
2025-06-10T12:22:22.020766Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.021019Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.021276Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.021754Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_links.ibd' OS error: 103
2025-06-10T12:22:22.022065Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.022325Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.023005Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.023646Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_links` because it could not be opened.
2025-06-10T12:22:22.024056Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.024361Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.024646Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.025032Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_newsletter.ibd' OS error: 103
2025-06-10T12:22:22.025473Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.025782Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.026212Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_newsletter`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.026810Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_newsletter` because it could not be opened.
2025-06-10T12:22:22.027243Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.027535Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.027813Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.028201Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_newsletter_emails.ibd' OS error: 103
2025-06-10T12:22:22.028587Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.028853Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.029273Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_newsletter_emails`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.030069Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_newsletter_emails` because it could not be opened.
2025-06-10T12:22:22.030581Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.030846Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.031110Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.031576Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_newsletter_sent.ibd' OS error: 103
2025-06-10T12:22:22.031909Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.032159Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.032645Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_newsletter_sent`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.033201Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_newsletter_sent` because it could not be opened.
2025-06-10T12:22:22.033776Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.034036Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.034364Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.034802Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_newsletter_stats.ibd' OS error: 103
2025-06-10T12:22:22.035154Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.035479Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.035894Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_newsletter_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.036573Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_newsletter_stats` because it could not be opened.
2025-06-10T12:22:22.037006Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.037324Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.037623Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.038009Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_newsletter_user_logs.ibd' OS error: 103
2025-06-10T12:22:22.038434Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.038697Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.039173Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_newsletter_user_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.040190Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_newsletter_user_logs` because it could not be opened.
2025-06-10T12:22:22.041531Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.041935Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.042209Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.042622Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_options.ibd' OS error: 103
2025-06-10T12:22:22.043012Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.043295Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.043753Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.044376Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_options` because it could not be opened.
2025-06-10T12:22:22.044799Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.045065Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.045397Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.045786Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_post_views.ibd' OS error: 103
2025-06-10T12:22:22.046126Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.046517Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.046980Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_post_views`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.047598Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_post_views` because it could not be opened.
2025-06-10T12:22:22.048059Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.048384Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.048707Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.049127Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:22.049493Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.049763Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.050359Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.050941Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_postmeta` because it could not be opened.
2025-06-10T12:22:22.051380Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.051670Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.051930Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.052327Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_posts.ibd' OS error: 103
2025-06-10T12:22:22.052685Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.052934Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.053370Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.053985Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_posts` because it could not be opened.
2025-06-10T12:22:22.054386Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.054645Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.054902Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.055275Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_revslider_css.ibd' OS error: 103
2025-06-10T12:22:22.055740Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.055987Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.056451Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_revslider_css`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.057002Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_revslider_css` because it could not be opened.
2025-06-10T12:22:22.057429Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.057685Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.057944Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.058387Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_revslider_css_bkp.ibd' OS error: 103
2025-06-10T12:22:22.058844Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.059104Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.059578Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_revslider_css_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.060129Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_revslider_css_bkp` because it could not be opened.
2025-06-10T12:22:22.060592Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.060865Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.061136Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.061564Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_revslider_layer_animations.ibd' OS error: 103
2025-06-10T12:22:22.061914Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.062162Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.062785Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_revslider_layer_animations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.063409Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_revslider_layer_animations` because it could not be opened.
2025-06-10T12:22:22.063829Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.064092Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.064390Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.064772Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_revslider_layer_animations_bkp.ibd' OS error: 103
2025-06-10T12:22:22.065145Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.065465Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.065896Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_revslider_layer_animations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.066534Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_revslider_layer_animations_bkp` because it could not be opened.
2025-06-10T12:22:22.066959Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.067223Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.067528Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.067918Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_revslider_navigations.ibd' OS error: 103
2025-06-10T12:22:22.068378Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.068642Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.069083Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_revslider_navigations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.069695Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_revslider_navigations` because it could not be opened.
2025-06-10T12:22:22.070103Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.070528Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.070873Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.071548Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_revslider_navigations_bkp.ibd' OS error: 103
2025-06-10T12:22:22.072151Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.073097Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.073808Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_revslider_navigations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.074570Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_revslider_navigations_bkp` because it could not be opened.
2025-06-10T12:22:22.075074Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.075351Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.075630Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.076064Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_revslider_sliders.ibd' OS error: 103
2025-06-10T12:22:22.076423Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.076696Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.077214Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_revslider_sliders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.077786Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_revslider_sliders` because it could not be opened.
2025-06-10T12:22:22.078329Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.078595Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.078865Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.079467Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_revslider_sliders_bkp.ibd' OS error: 103
2025-06-10T12:22:22.079835Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.080148Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.080585Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_revslider_sliders_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.081269Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_revslider_sliders_bkp` because it could not be opened.
2025-06-10T12:22:22.081747Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.082036Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.082335Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.082749Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_revslider_slides.ibd' OS error: 103
2025-06-10T12:22:22.083328Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.083702Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.084160Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_revslider_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.084715Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_revslider_slides` because it could not be opened.
2025-06-10T12:22:22.085228Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.085483Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.085742Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.086191Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_revslider_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:22.086560Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.086833Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.087313Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_revslider_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.087948Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_revslider_slides_bkp` because it could not be opened.
2025-06-10T12:22:22.088466Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.088815Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.089120Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.089483Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_revslider_static_slides.ibd' OS error: 103
2025-06-10T12:22:22.089980Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.090307Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.090707Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_revslider_static_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.091439Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_revslider_static_slides` because it could not be opened.
2025-06-10T12:22:22.091845Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.092235Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.092532Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.092894Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_revslider_static_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:22.093344Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.093605Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.094078Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_revslider_static_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.094730Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_revslider_static_slides_bkp` because it could not be opened.
2025-06-10T12:22:22.095251Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.095515Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.095775Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.096212Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:22.096549Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.096800Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.097267Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.097826Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:22.098314Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.098570Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.098829Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.099264Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:22.099590Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.099959Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.100373Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.101077Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:22.101545Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.102104Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.102380Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.102812Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:22.103333Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.103660Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.104654Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.105320Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_termmeta` because it could not be opened.
2025-06-10T12:22:22.105732Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.106066Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.106363Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.107101Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_terms.ibd' OS error: 103
2025-06-10T12:22:22.107433Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.107695Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.108250Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.108884Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_terms` because it could not be opened.
2025-06-10T12:22:22.109340Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.109611Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.109932Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.110320Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:22.110652Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.110993Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.111413Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.112078Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_usermeta` because it could not be opened.
2025-06-10T12:22:22.112480Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.112818Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.113094Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.113498Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_users.ibd' OS error: 103
2025-06-10T12:22:22.113929Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.114217Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.114615Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.115248Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_users` because it could not be opened.
2025-06-10T12:22:22.115966Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.116223Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.116482Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.116940Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_wfblockediplog.ibd' OS error: 103
2025-06-10T12:22:22.117272Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.117518Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.118019Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_wfblockediplog`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.118764Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_wfblockediplog` because it could not be opened.
2025-06-10T12:22:22.119175Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.119423Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.119755Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.120161Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_wfblocks7.ibd' OS error: 103
2025-06-10T12:22:22.120476Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.120871Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.121287Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_wfblocks7`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.121974Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_wfblocks7` because it could not be opened.
2025-06-10T12:22:22.122397Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.122670Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.123082Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.123571Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_wfconfig.ibd' OS error: 103
2025-06-10T12:22:22.123958Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.124227Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.124639Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_wfconfig`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.125226Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_wfconfig` because it could not be opened.
2025-06-10T12:22:22.125619Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.125923Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.126195Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.126577Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_wfcrawlers.ibd' OS error: 103
2025-06-10T12:22:22.126947Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.127207Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.127622Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_wfcrawlers`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.128215Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_wfcrawlers` because it could not be opened.
2025-06-10T12:22:22.128631Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.128949Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.129259Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.129726Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_wffilechanges.ibd' OS error: 103
2025-06-10T12:22:22.130083Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.130344Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.130819Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_wffilechanges`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.131378Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_wffilechanges` because it could not be opened.
2025-06-10T12:22:22.131880Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.132139Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.132448Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.132943Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_wffilemods.ibd' OS error: 103
2025-06-10T12:22:22.133297Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.133549Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.134052Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_wffilemods`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.134667Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_wffilemods` because it could not be opened.
2025-06-10T12:22:22.135174Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.135511Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.136018Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.136515Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_wfhits.ibd' OS error: 103
2025-06-10T12:22:22.137038Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.137678Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.138230Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_wfhits`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.139072Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_wfhits` because it could not be opened.
2025-06-10T12:22:22.139565Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.139878Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.140156Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.140553Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_wfhoover.ibd' OS error: 103
2025-06-10T12:22:22.140905Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.141165Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.141597Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_wfhoover`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.142167Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_wfhoover` because it could not be opened.
2025-06-10T12:22:22.142616Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.142890Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.143163Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.143581Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_wfissues.ibd' OS error: 103
2025-06-10T12:22:22.143922Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.144193Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.144666Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_wfissues`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.145251Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_wfissues` because it could not be opened.
2025-06-10T12:22:22.145753Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.146026Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.146323Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.146708Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_wfknownfilelist.ibd' OS error: 103
2025-06-10T12:22:22.147174Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.147526Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.147924Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_wfknownfilelist`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.148555Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_wfknownfilelist` because it could not be opened.
2025-06-10T12:22:22.149186Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.149502Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.149788Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.150174Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_wflivetraffichuman.ibd' OS error: 103
2025-06-10T12:22:22.150572Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.150832Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.151276Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_wflivetraffichuman`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.151872Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_wflivetraffichuman` because it could not be opened.
2025-06-10T12:22:22.152327Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.152598Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.152871Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.153288Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_wflocs.ibd' OS error: 103
2025-06-10T12:22:22.153615Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.153872Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.154388Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_wflocs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.155099Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_wflocs` because it could not be opened.
2025-06-10T12:22:22.155563Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.155867Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.156179Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.156615Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_wflogins.ibd' OS error: 103
2025-06-10T12:22:22.156941Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.157224Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.157667Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_wflogins`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.158271Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_wflogins` because it could not be opened.
2025-06-10T12:22:22.158650Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.158900Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.159158Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.159592Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_wfls_2fa_secrets.ibd' OS error: 103
2025-06-10T12:22:22.159921Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.160197Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.160673Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_wfls_2fa_secrets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.161300Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_wfls_2fa_secrets` because it could not be opened.
2025-06-10T12:22:22.161708Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.161966Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.162279Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.162686Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_wfls_settings.ibd' OS error: 103
2025-06-10T12:22:22.163032Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.163315Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.163730Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_wfls_settings`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.164336Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_wfls_settings` because it could not be opened.
2025-06-10T12:22:22.164798Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.165102Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.165442Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.165825Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_wfnotifications.ibd' OS error: 103
2025-06-10T12:22:22.166151Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.166502Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.166898Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_wfnotifications`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.167621Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_wfnotifications` because it could not be opened.
2025-06-10T12:22:22.168188Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.168496Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.169127Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.169505Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_wfpendingissues.ibd' OS error: 103
2025-06-10T12:22:22.169999Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.170786Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.171263Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_wfpendingissues`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.171892Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_wfpendingissues` because it could not be opened.
2025-06-10T12:22:22.172329Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.172601Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.172906Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.173301Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_wfreversecache.ibd' OS error: 103
2025-06-10T12:22:22.173647Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.173939Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.174360Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_wfreversecache`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.175000Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_wfreversecache` because it could not be opened.
2025-06-10T12:22:22.175450Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.175724Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.176036Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.176427Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_wfsnipcache.ibd' OS error: 103
2025-06-10T12:22:22.176781Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.177081Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.177515Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_wfsnipcache`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.178145Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_wfsnipcache` because it could not be opened.
2025-06-10T12:22:22.178626Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.178921Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.179193Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.179579Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_wfstatus.ibd' OS error: 103
2025-06-10T12:22:22.179940Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.180205Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.180628Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_wfstatus`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.181293Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_wfstatus` because it could not be opened.
2025-06-10T12:22:22.181696Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.182010Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.182279Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.182664Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_wftrafficrates.ibd' OS error: 103
2025-06-10T12:22:22.183048Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.183310Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.183722Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_wftrafficrates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.184337Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_wftrafficrates` because it could not be opened.
2025-06-10T12:22:22.184742Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.185023Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.185296Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.185684Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_wpfm_backup.ibd' OS error: 103
2025-06-10T12:22:22.186047Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.186310Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.186761Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_wpfm_backup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.187440Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_wpfm_backup` because it could not be opened.
2025-06-10T12:22:22.187920Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.188191Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.188470Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.188896Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_yoast_seo_links.ibd' OS error: 103
2025-06-10T12:22:22.189290Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.189594Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.190048Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_yoast_seo_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.190639Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_yoast_seo_links` because it could not be opened.
2025-06-10T12:22:22.191071Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.191340Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.191613Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.192040Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem21\wp_yoast_seo_meta.ibd' OS error: 103
2025-06-10T12:22:22.192389Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.192879Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.193316Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem21/wp_yoast_seo_meta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.193959Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem21/wp_yoast_seo_meta` because it could not be opened.
2025-06-10T12:22:22.194631Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.194924Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.195199Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.195596Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:22.196002Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.196273Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.196760Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.197359Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:22.198073Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.198347Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.198610Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.199092Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_comments.ibd' OS error: 103
2025-06-10T12:22:22.199424Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.199705Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.200161Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.200826Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_comments` because it could not be opened.
2025-06-10T12:22:22.201263Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.201530Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.201867Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.202342Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:22.202888Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.203183Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.203604Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.204267Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_fbv` because it could not be opened.
2025-06-10T12:22:22.204728Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.205003Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.205279Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.205703Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:22.206062Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.206312Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.206799Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.207463Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:22.208055Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.208318Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.208578Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.209095Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_gg_attributes.ibd' OS error: 103
2025-06-10T12:22:22.209613Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.210021Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.210490Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_gg_attributes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.211122Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_gg_attributes` because it could not be opened.
2025-06-10T12:22:22.211564Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.212142Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.212433Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.212905Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_gg_cdn.ibd' OS error: 103
2025-06-10T12:22:22.213227Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.213480Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.213981Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_gg_cdn`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.214518Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_gg_cdn` because it could not be opened.
2025-06-10T12:22:22.215004Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.215271Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.215539Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.216010Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_gg_folders.ibd' OS error: 103
2025-06-10T12:22:22.216326Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.216576Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.217075Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_gg_folders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.217707Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_gg_folders` because it could not be opened.
2025-06-10T12:22:22.218107Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.218377Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.218742Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.219130Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_gg_galleries.ibd' OS error: 103
2025-06-10T12:22:22.219504Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.219895Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.220295Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_gg_galleries`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.220937Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_gg_galleries` because it could not be opened.
2025-06-10T12:22:22.221327Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.221583Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.221964Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.222327Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_gg_galleries_excluded.ibd' OS error: 103
2025-06-10T12:22:22.222756Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.223009Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.223399Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_gg_galleries_excluded`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.224047Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_gg_galleries_excluded` because it could not be opened.
2025-06-10T12:22:22.224576Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.224947Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.225210Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.225644Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_gg_galleries_resources.ibd' OS error: 103
2025-06-10T12:22:22.226065Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.226317Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.226799Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_gg_galleries_resources`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.227366Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_gg_galleries_resources` because it could not be opened.
2025-06-10T12:22:22.227828Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.228094Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.228353Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.228863Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_gg_image_optimize.ibd' OS error: 103
2025-06-10T12:22:22.229208Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.229471Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.229898Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_gg_image_optimize`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.230487Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_gg_image_optimize` because it could not be opened.
2025-06-10T12:22:22.230970Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.231222Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.231480Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.231931Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_gg_membership_presets.ibd' OS error: 103
2025-06-10T12:22:22.232266Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.232516Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.233015Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_gg_membership_presets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.233661Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_gg_membership_presets` because it could not be opened.
2025-06-10T12:22:22.234133Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.234385Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.234727Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.235114Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_gg_photos.ibd' OS error: 103
2025-06-10T12:22:22.235443Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.235779Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.236242Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_gg_photos`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.236841Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_gg_photos` because it could not be opened.
2025-06-10T12:22:22.237222Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.237475Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.237829Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.238195Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_gg_photos_pos.ibd' OS error: 103
2025-06-10T12:22:22.238519Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.238891Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.239286Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_gg_photos_pos`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.239915Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_gg_photos_pos` because it could not be opened.
2025-06-10T12:22:22.240300Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.240614Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.240891Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.241256Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_gg_photos_settings.ibd' OS error: 103
2025-06-10T12:22:22.241702Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.242161Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.242606Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_gg_photos_settings`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.243214Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_gg_photos_settings` because it could not be opened.
2025-06-10T12:22:22.243696Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.244045Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.244358Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.244781Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_gg_settings_presets.ibd' OS error: 103
2025-06-10T12:22:22.245122Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.245388Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.245901Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_gg_settings_presets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.246577Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_gg_settings_presets` because it could not be opened.
2025-06-10T12:22:22.247054Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.247319Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.247832Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.248369Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_gg_settings_sets.ibd' OS error: 103
2025-06-10T12:22:22.249169Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.249514Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.250106Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_gg_settings_sets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.250877Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_gg_settings_sets` because it could not be opened.
2025-06-10T12:22:22.251401Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.251696Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.251997Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.252384Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_gg_stats.ibd' OS error: 103
2025-06-10T12:22:22.252736Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.253008Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.253447Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_gg_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.254051Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_gg_stats` because it could not be opened.
2025-06-10T12:22:22.254537Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.254814Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.255095Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.255533Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_gg_tags.ibd' OS error: 103
2025-06-10T12:22:22.255914Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.256181Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.256621Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_gg_tags`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.257203Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_gg_tags` because it could not be opened.
2025-06-10T12:22:22.257689Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.257972Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.258281Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.258682Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_links.ibd' OS error: 103
2025-06-10T12:22:22.259008Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.259274Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.259738Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.260329Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_links` because it could not be opened.
2025-06-10T12:22:22.260794Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.261051Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.261317Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.261747Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_newsletter.ibd' OS error: 103
2025-06-10T12:22:22.262068Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.262471Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.262913Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_newsletter`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.263516Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_newsletter` because it could not be opened.
2025-06-10T12:22:22.263956Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.264213Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.264559Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.265129Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_newsletter_emails.ibd' OS error: 103
2025-06-10T12:22:22.265680Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.265931Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.266333Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_newsletter_emails`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.266946Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_newsletter_emails` because it could not be opened.
2025-06-10T12:22:22.267327Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.267648Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.267907Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.268268Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_newsletter_sent.ibd' OS error: 103
2025-06-10T12:22:22.268738Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.269020Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.269491Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_newsletter_sent`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.270050Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_newsletter_sent` because it could not be opened.
2025-06-10T12:22:22.270538Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.270836Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.271207Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.271906Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_newsletter_stats.ibd' OS error: 103
2025-06-10T12:22:22.272277Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.272639Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.273026Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_newsletter_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.273690Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_newsletter_stats` because it could not be opened.
2025-06-10T12:22:22.274087Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.274337Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.274695Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.275150Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_newsletter_user_logs.ibd' OS error: 103
2025-06-10T12:22:22.275609Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.275868Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.276297Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_newsletter_user_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.277000Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_newsletter_user_logs` because it could not be opened.
2025-06-10T12:22:22.277570Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.277867Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.278129Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.278662Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_options.ibd' OS error: 103
2025-06-10T12:22:22.279298Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.279703Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.280159Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.280770Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_options` because it could not be opened.
2025-06-10T12:22:22.281176Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.281475Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.281804Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.282252Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_post_views.ibd' OS error: 103
2025-06-10T12:22:22.282671Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.282948Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.284021Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_post_views`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.284638Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_post_views` because it could not be opened.
2025-06-10T12:22:22.285757Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.286055Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.286335Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.286741Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:22.287075Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.287343Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.287829Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.288424Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_postmeta` because it could not be opened.
2025-06-10T12:22:22.288843Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.289119Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.289630Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.290241Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_posts.ibd' OS error: 103
2025-06-10T12:22:22.290623Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.290902Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.291334Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.291991Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_posts` because it could not be opened.
2025-06-10T12:22:22.292582Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.292985Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.293254Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.293728Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_revslider_css.ibd' OS error: 103
2025-06-10T12:22:22.294069Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.294321Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.294847Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_revslider_css`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.295470Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_revslider_css` because it could not be opened.
2025-06-10T12:22:22.295884Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.296140Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.296443Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.296871Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_revslider_css_bkp.ibd' OS error: 103
2025-06-10T12:22:22.297201Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.297515Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.297922Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_revslider_css_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.298541Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_revslider_css_bkp` because it could not be opened.
2025-06-10T12:22:22.298915Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.299167Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.299472Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.299845Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_revslider_layer_animations.ibd' OS error: 103
2025-06-10T12:22:22.300192Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.300520Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.300924Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_revslider_layer_animations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.301552Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_revslider_layer_animations` because it could not be opened.
2025-06-10T12:22:22.301938Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.302190Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.302549Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.302927Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_revslider_layer_animations_bkp.ibd' OS error: 103
2025-06-10T12:22:22.303285Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.303614Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.304003Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_revslider_layer_animations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.304671Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_revslider_layer_animations_bkp` because it could not be opened.
2025-06-10T12:22:22.305070Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.305324Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.305704Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.306082Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_revslider_navigations.ibd' OS error: 103
2025-06-10T12:22:22.306484Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.306746Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.307142Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_revslider_navigations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.307779Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_revslider_navigations` because it could not be opened.
2025-06-10T12:22:22.308257Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.308828Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.309170Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.309592Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_revslider_navigations_bkp.ibd' OS error: 103
2025-06-10T12:22:22.310005Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.310308Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.310796Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_revslider_navigations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.311690Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_revslider_navigations_bkp` because it could not be opened.
2025-06-10T12:22:22.312669Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.312945Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.313328Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.313723Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_revslider_sliders.ibd' OS error: 103
2025-06-10T12:22:22.314426Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.314688Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.315165Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_revslider_sliders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.315840Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_revslider_sliders` because it could not be opened.
2025-06-10T12:22:22.316279Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.316566Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.316843Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.317226Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_revslider_sliders_bkp.ibd' OS error: 103
2025-06-10T12:22:22.317613Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.317882Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.318302Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_revslider_sliders_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.318938Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_revslider_sliders_bkp` because it could not be opened.
2025-06-10T12:22:22.319423Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.319704Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.319983Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.320369Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_revslider_slides.ibd' OS error: 103
2025-06-10T12:22:22.320787Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.321090Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.321545Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_revslider_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.322198Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_revslider_slides` because it could not be opened.
2025-06-10T12:22:22.322708Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.322965Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.323234Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.323665Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_revslider_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:22.324007Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.324259Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.324753Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_revslider_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.325339Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_revslider_slides_bkp` because it could not be opened.
2025-06-10T12:22:22.325811Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.326073Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.326335Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.326780Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_revslider_static_slides.ibd' OS error: 103
2025-06-10T12:22:22.327128Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.327468Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.327955Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_revslider_static_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.328633Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_revslider_static_slides` because it could not be opened.
2025-06-10T12:22:22.329050Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.329313Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.329674Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.330042Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_revslider_static_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:22.330499Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.330812Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.331212Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_revslider_static_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.331885Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_revslider_static_slides_bkp` because it could not be opened.
2025-06-10T12:22:22.332278Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.332665Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.332922Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.333286Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:22.333731Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.333983Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.334524Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.335074Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:22.335542Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.335936Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.336195Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.336662Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:22.336985Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.337242Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.337836Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.338453Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:22.338857Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.339119Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.339458Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.339843Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:22.340274Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.340570Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.340986Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.341619Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_termmeta` because it could not be opened.
2025-06-10T12:22:22.341990Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.342240Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.342622Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.342998Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_terms.ibd' OS error: 103
2025-06-10T12:22:22.343719Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.345277Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.345913Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.346637Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_terms` because it could not be opened.
2025-06-10T12:22:22.347121Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.347392Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.347661Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.348243Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:22.348622Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.348881Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.349358Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.349999Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_usermeta` because it could not be opened.
2025-06-10T12:22:22.350454Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.350717Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.351058Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.351494Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_users.ibd' OS error: 103
2025-06-10T12:22:22.351805Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.352137Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.352569Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.353285Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_users` because it could not be opened.
2025-06-10T12:22:22.353723Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.354105Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.354448Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.354861Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_wfblockediplog.ibd' OS error: 103
2025-06-10T12:22:22.355333Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.355601Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.356120Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_wfblockediplog`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.356700Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_wfblockediplog` because it could not be opened.
2025-06-10T12:22:22.357191Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.357538Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.357813Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.358260Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_wfblocks7.ibd' OS error: 103
2025-06-10T12:22:22.358578Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.358832Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.359325Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_wfblocks7`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.359873Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_wfblocks7` because it could not be opened.
2025-06-10T12:22:22.360314Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.360570Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.360897Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.361422Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_wfconfig.ibd' OS error: 103
2025-06-10T12:22:22.361736Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.362086Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.362550Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_wfconfig`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.363154Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_wfconfig` because it could not be opened.
2025-06-10T12:22:22.363519Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.363770Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.364087Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.364461Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_wfcrawlers.ibd' OS error: 103
2025-06-10T12:22:22.364773Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.365100Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.365563Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_wfcrawlers`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.366212Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_wfcrawlers` because it could not be opened.
2025-06-10T12:22:22.366565Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.366813Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.367188Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.367549Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_wffilechanges.ibd' OS error: 103
2025-06-10T12:22:22.367865Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.368251Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.368639Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_wffilechanges`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.369357Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_wffilechanges` because it could not be opened.
2025-06-10T12:22:22.369786Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.370130Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.370390Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.370755Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_wffilemods.ibd' OS error: 103
2025-06-10T12:22:22.371144Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.371481Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.371956Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_wffilemods`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.372574Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_wffilemods` because it could not be opened.
2025-06-10T12:22:22.373016Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.373288Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.373575Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.374027Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_wfhits.ibd' OS error: 103
2025-06-10T12:22:22.374419Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.374683Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.375136Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_wfhits`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.375765Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_wfhits` because it could not be opened.
2025-06-10T12:22:22.376199Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.376461Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.377147Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.378873Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_wfhoover.ibd' OS error: 103
2025-06-10T12:22:22.379245Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.379627Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.380099Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_wfhoover`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.380738Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_wfhoover` because it could not be opened.
2025-06-10T12:22:22.381315Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.381605Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.381878Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.382293Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_wfissues.ibd' OS error: 103
2025-06-10T12:22:22.382684Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.382960Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.383382Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_wfissues`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.384019Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_wfissues` because it could not be opened.
2025-06-10T12:22:22.384485Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.384763Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.385044Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.385492Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_wfknownfilelist.ibd' OS error: 103
2025-06-10T12:22:22.386045Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.386320Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.386764Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_wfknownfilelist`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.387607Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_wfknownfilelist` because it could not be opened.
2025-06-10T12:22:22.388099Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.388360Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.388710Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.389218Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_wflivetraffichuman.ibd' OS error: 103
2025-06-10T12:22:22.389717Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.389971Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.390439Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_wflivetraffichuman`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.391046Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_wflivetraffichuman` because it could not be opened.
2025-06-10T12:22:22.391505Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.391774Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.392033Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.392450Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_wflocs.ibd' OS error: 103
2025-06-10T12:22:22.392783Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.393031Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.393531Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_wflocs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.394158Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_wflocs` because it could not be opened.
2025-06-10T12:22:22.394631Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.394891Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.395156Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.395649Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_wflogins.ibd' OS error: 103
2025-06-10T12:22:22.396058Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.396313Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.396771Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_wflogins`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.397311Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_wflogins` because it could not be opened.
2025-06-10T12:22:22.397816Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.398081Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.398362Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.398753Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_wfls_2fa_secrets.ibd' OS error: 103
2025-06-10T12:22:22.399103Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.399391Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.399831Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_wfls_2fa_secrets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.400486Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_wfls_2fa_secrets` because it could not be opened.
2025-06-10T12:22:22.400880Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.401143Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.401594Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.401985Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_wfls_settings.ibd' OS error: 103
2025-06-10T12:22:22.402326Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.402655Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.403109Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_wfls_settings`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.403707Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_wfls_settings` because it could not be opened.
2025-06-10T12:22:22.404152Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.404507Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.404826Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.405195Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_wfnotifications.ibd' OS error: 103
2025-06-10T12:22:22.405662Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.405912Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.406669Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_wfnotifications`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.407398Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_wfnotifications` because it could not be opened.
2025-06-10T12:22:22.407934Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.408409Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.408816Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.409316Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_wfpendingissues.ibd' OS error: 103
2025-06-10T12:22:22.409892Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.410317Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.410800Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_wfpendingissues`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.411452Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_wfpendingissues` because it could not be opened.
2025-06-10T12:22:22.411932Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.412199Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.412532Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.412918Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_wfreversecache.ibd' OS error: 103
2025-06-10T12:22:22.413256Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.413585Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.414002Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_wfreversecache`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.414653Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_wfreversecache` because it could not be opened.
2025-06-10T12:22:22.415100Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.415445Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.415723Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.416130Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_wfsnipcache.ibd' OS error: 103
2025-06-10T12:22:22.416701Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.417127Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.417868Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_wfsnipcache`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.418803Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_wfsnipcache` because it could not be opened.
2025-06-10T12:22:22.419514Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.419921Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.420400Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.420977Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_wfstatus.ibd' OS error: 103
2025-06-10T12:22:22.421546Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.421933Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.422374Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_wfstatus`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.422942Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_wfstatus` because it could not be opened.
2025-06-10T12:22:22.423425Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.423703Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.423978Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.424436Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_wftrafficrates.ibd' OS error: 103
2025-06-10T12:22:22.424774Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.425044Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.425512Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_wftrafficrates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.426084Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_wftrafficrates` because it could not be opened.
2025-06-10T12:22:22.426536Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.426800Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.427071Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.427514Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_wpfm_backup.ibd' OS error: 103
2025-06-10T12:22:22.427847Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.428110Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.428585Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_wpfm_backup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.429149Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_wpfm_backup` because it could not be opened.
2025-06-10T12:22:22.429625Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.429896Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.430166Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.430568Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_yoast_seo_links.ibd' OS error: 103
2025-06-10T12:22:22.430909Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.431171Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.431634Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_yoast_seo_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.432213Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_yoast_seo_links` because it could not be opened.
2025-06-10T12:22:22.432717Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.433000Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.433303Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.433729Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem3\wp_yoast_seo_meta.ibd' OS error: 103
2025-06-10T12:22:22.434150Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.434470Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.434867Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem3/wp_yoast_seo_meta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.435532Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem3/wp_yoast_seo_meta` because it could not be opened.
2025-06-10T12:22:22.436357Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.436752Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.437096Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.437553Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_actionscheduler_actions.ibd' OS error: 103
2025-06-10T12:22:22.437937Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.438203Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.438732Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_actionscheduler_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.439434Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_actionscheduler_actions` because it could not be opened.
2025-06-10T12:22:22.439954Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.440219Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.440997Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.442178Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_actionscheduler_claims.ibd' OS error: 103
2025-06-10T12:22:22.442970Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.443244Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.443695Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_actionscheduler_claims`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.444334Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_actionscheduler_claims` because it could not be opened.
2025-06-10T12:22:22.444827Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.445099Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.445373Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.445785Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_actionscheduler_groups.ibd' OS error: 103
2025-06-10T12:22:22.446142Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.446434Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.446860Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_actionscheduler_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.447505Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_actionscheduler_groups` because it could not be opened.
2025-06-10T12:22:22.448091Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.448376Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.448872Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.449342Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_actionscheduler_logs.ibd' OS error: 103
2025-06-10T12:22:22.449752Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.450038Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.450793Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_actionscheduler_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.451456Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_actionscheduler_logs` because it could not be opened.
2025-06-10T12:22:22.451914Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.452178Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.452493Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.452876Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:22.453213Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.453518Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.453929Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.454546Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:22.455085Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.455360Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.455725Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.456223Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_comments.ibd' OS error: 103
2025-06-10T12:22:22.456635Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.456889Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.457285Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.457919Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_comments` because it could not be opened.
2025-06-10T12:22:22.458314Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.458610Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.458883Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.459268Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_csshero4.ibd' OS error: 103
2025-06-10T12:22:22.459685Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.459950Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.460342Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_csshero4`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.460989Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_csshero4` because it could not be opened.
2025-06-10T12:22:22.461458Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.461736Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.462012Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.462430Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:22.462760Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.463029Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.463487Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.464095Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_fbv` because it could not be opened.
2025-06-10T12:22:22.464508Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.464780Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.465054Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.465474Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:22.465835Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.466100Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.466627Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.467377Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:22.467834Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.468270Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.468608Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.469039Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_gg_attributes.ibd' OS error: 103
2025-06-10T12:22:22.469441Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.469717Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.470138Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_gg_attributes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.470771Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_gg_attributes` because it could not be opened.
2025-06-10T12:22:22.471205Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.471513Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.471787Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.472264Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_gg_cdn.ibd' OS error: 103
2025-06-10T12:22:22.472734Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.473044Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.473763Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_gg_cdn`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.474581Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_gg_cdn` because it could not be opened.
2025-06-10T12:22:22.475220Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.475498Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.475776Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.476226Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_gg_folders.ibd' OS error: 103
2025-06-10T12:22:22.476559Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.476820Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.477298Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_gg_folders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.477872Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_gg_folders` because it could not be opened.
2025-06-10T12:22:22.478379Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.478645Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.478977Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.479382Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_gg_galleries.ibd' OS error: 103
2025-06-10T12:22:22.479722Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.480074Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.480494Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_gg_galleries`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.481192Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_gg_galleries` because it could not be opened.
2025-06-10T12:22:22.481700Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.482102Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.482385Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.482750Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_gg_galleries_excluded.ibd' OS error: 103
2025-06-10T12:22:22.483195Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.483447Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.483978Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_gg_galleries_excluded`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.484571Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_gg_galleries_excluded` because it could not be opened.
2025-06-10T12:22:22.485459Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.485759Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.486125Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.486534Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_gg_galleries_resources.ibd' OS error: 103
2025-06-10T12:22:22.487031Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.487306Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.487691Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_gg_galleries_resources`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.488398Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_gg_galleries_resources` because it could not be opened.
2025-06-10T12:22:22.488816Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.489210Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.489468Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.489826Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_gg_image_optimize.ibd' OS error: 103
2025-06-10T12:22:22.490298Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.490542Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.491018Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_gg_image_optimize`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.491555Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_gg_image_optimize` because it could not be opened.
2025-06-10T12:22:22.492022Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.492340Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.492587Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.493041Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_gg_membership_presets.ibd' OS error: 103
2025-06-10T12:22:22.493373Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.493614Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.494172Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_gg_membership_presets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.494737Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_gg_membership_presets` because it could not be opened.
2025-06-10T12:22:22.495228Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.495472Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.495726Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.496290Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_gg_photos.ibd' OS error: 103
2025-06-10T12:22:22.496661Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.497008Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.497508Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_gg_photos`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.498164Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_gg_photos` because it could not be opened.
2025-06-10T12:22:22.498605Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.498924Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.499207Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.499567Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_gg_photos_pos.ibd' OS error: 103
2025-06-10T12:22:22.499991Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.500264Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.500702Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_gg_photos_pos`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.501420Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_gg_photos_pos` because it could not be opened.
2025-06-10T12:22:22.501832Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.502217Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.502474Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.502907Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_gg_photos_settings.ibd' OS error: 103
2025-06-10T12:22:22.503300Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.503563Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.504053Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_gg_photos_settings`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.506337Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_gg_photos_settings` because it could not be opened.
2025-06-10T12:22:22.507237Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.507546Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.507825Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.508240Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_gg_settings_presets.ibd' OS error: 103
2025-06-10T12:22:22.508594Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.508889Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.509604Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_gg_settings_presets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.510260Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_gg_settings_presets` because it could not be opened.
2025-06-10T12:22:22.510747Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.511072Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.511467Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.512019Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_gg_settings_sets.ibd' OS error: 103
2025-06-10T12:22:22.512454Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.512738Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.513206Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_gg_settings_sets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.513868Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_gg_settings_sets` because it could not be opened.
2025-06-10T12:22:22.514482Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.514769Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.515125Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.515494Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_gg_stats.ibd' OS error: 103
2025-06-10T12:22:22.515849Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.516298Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.516707Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_gg_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.517341Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_gg_stats` because it could not be opened.
2025-06-10T12:22:22.517718Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.518075Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.518405Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.518775Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_gg_tags.ibd' OS error: 103
2025-06-10T12:22:22.519190Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.519441Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.519902Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_gg_tags`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.520454Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_gg_tags` because it could not be opened.
2025-06-10T12:22:22.520847Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.521143Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.521404Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.521771Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_links.ibd' OS error: 103
2025-06-10T12:22:22.522181Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.522435Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.522889Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.523504Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_links` because it could not be opened.
2025-06-10T12:22:22.523905Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.524242Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.524501Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.524946Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_options.ibd' OS error: 103
2025-06-10T12:22:22.525292Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.525544Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.526012Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.526549Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_options` because it could not be opened.
2025-06-10T12:22:22.527003Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.527259Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.527521Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.527990Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_post_views.ibd' OS error: 103
2025-06-10T12:22:22.528325Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.528583Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.529065Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_post_views`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.529610Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_post_views` because it could not be opened.
2025-06-10T12:22:22.530049Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.530303Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.530564Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.531072Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:22.531512Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.531825Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.532364Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.532979Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_postmeta` because it could not be opened.
2025-06-10T12:22:22.533502Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.533768Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.534089Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.534507Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_posts.ibd' OS error: 103
2025-06-10T12:22:22.534907Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.535172Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.535567Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.536171Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_posts` because it could not be opened.
2025-06-10T12:22:22.536523Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.536819Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.537114Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.537480Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_redirection_404.ibd' OS error: 103
2025-06-10T12:22:22.537920Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.538220Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.538620Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_redirection_404`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.539266Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_redirection_404` because it could not be opened.
2025-06-10T12:22:22.539655Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.540034Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.540408Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.540855Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_redirection_groups.ibd' OS error: 103
2025-06-10T12:22:22.541206Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.541455Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.542068Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_redirection_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.542796Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_redirection_groups` because it could not be opened.
2025-06-10T12:22:22.543242Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.543496Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.543842Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.544226Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_redirection_items.ibd' OS error: 103
2025-06-10T12:22:22.544559Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.544883Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.545295Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_redirection_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.545960Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_redirection_items` because it could not be opened.
2025-06-10T12:22:22.546356Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.546657Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.547014Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.547398Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_redirection_logs.ibd' OS error: 103
2025-06-10T12:22:22.547846Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.548113Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.548536Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_redirection_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.549188Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_redirection_logs` because it could not be opened.
2025-06-10T12:22:22.549590Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.549918Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.550178Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.550548Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_revslider_css.ibd' OS error: 103
2025-06-10T12:22:22.551057Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.551309Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.552164Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_revslider_css`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.554628Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_revslider_css` because it could not be opened.
2025-06-10T12:22:22.555112Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.555461Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.555774Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.556197Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_revslider_css_bkp.ibd' OS error: 103
2025-06-10T12:22:22.556635Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.556946Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.557357Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_revslider_css_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.558022Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_revslider_css_bkp` because it could not be opened.
2025-06-10T12:22:22.558491Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.558797Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.559070Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.559468Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_revslider_layer_animations.ibd' OS error: 103
2025-06-10T12:22:22.559908Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.560184Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.560641Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_revslider_layer_animations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.561447Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_revslider_layer_animations` because it could not be opened.
2025-06-10T12:22:22.562166Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.562462Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.562776Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.563163Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_revslider_layer_animations_bkp.ibd' OS error: 103
2025-06-10T12:22:22.563540Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.563841Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.564257Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_revslider_layer_animations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.564910Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_revslider_layer_animations_bkp` because it could not be opened.
2025-06-10T12:22:22.565358Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.565622Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.565930Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.566313Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_revslider_navigations.ibd' OS error: 103
2025-06-10T12:22:22.566681Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.566971Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.567388Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_revslider_navigations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.568020Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_revslider_navigations` because it could not be opened.
2025-06-10T12:22:22.568412Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.568700Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.568987Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.569364Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_revslider_navigations_bkp.ibd' OS error: 103
2025-06-10T12:22:22.569818Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.570089Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.570510Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_revslider_navigations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.571160Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_revslider_navigations_bkp` because it could not be opened.
2025-06-10T12:22:22.571568Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.571872Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.572142Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.572525Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_revslider_sliders.ibd' OS error: 103
2025-06-10T12:22:22.572978Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.573293Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.573768Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_revslider_sliders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.574352Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_revslider_sliders` because it could not be opened.
2025-06-10T12:22:22.574792Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.575057Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.575327Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.575779Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_revslider_sliders_bkp.ibd' OS error: 103
2025-06-10T12:22:22.576156Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.576418Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.576898Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_revslider_sliders_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.577492Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_revslider_sliders_bkp` because it could not be opened.
2025-06-10T12:22:22.578015Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.578315Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.578604Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.579045Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_revslider_slides.ibd' OS error: 103
2025-06-10T12:22:22.579472Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.579765Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.580196Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_revslider_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.580858Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_revslider_slides` because it could not be opened.
2025-06-10T12:22:22.581301Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.581575Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.581892Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.582277Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_revslider_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:22.582660Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.582933Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.583450Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_revslider_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.584106Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_revslider_slides_bkp` because it could not be opened.
2025-06-10T12:22:22.584580Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.584854Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.585161Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.585586Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_revslider_static_slides.ibd' OS error: 103
2025-06-10T12:22:22.586352Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.586661Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.587105Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_revslider_static_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.587712Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_revslider_static_slides` because it could not be opened.
2025-06-10T12:22:22.588216Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.588475Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.588738Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.589186Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_revslider_static_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:22.589561Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.589817Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.590703Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_revslider_static_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.591520Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_revslider_static_slides_bkp` because it could not be opened.
2025-06-10T12:22:22.592119Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.592671Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.593320Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.594007Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_rich_web_icons.ibd' OS error: 103
2025-06-10T12:22:22.594614Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.594878Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.595339Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_rich_web_icons`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.595931Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_rich_web_icons` because it could not be opened.
2025-06-10T12:22:22.596429Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.596689Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.596988Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.597448Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_rich_web_timeline_manager.ibd' OS error: 103
2025-06-10T12:22:22.597805Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.598166Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.598852Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_rich_web_timeline_manager`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.599725Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_rich_web_timeline_manager` because it could not be opened.
2025-06-10T12:22:22.600280Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.600543Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.600874Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.601486Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_rich_web_timeline_options.ibd' OS error: 103
2025-06-10T12:22:22.601900Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.602207Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.602609Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_rich_web_timeline_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.603282Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_rich_web_timeline_options` because it could not be opened.
2025-06-10T12:22:22.603730Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.604045Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.604371Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.604817Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_rich_web_timeline_short_options.ibd' OS error: 103
2025-06-10T12:22:22.605313Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.605590Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.606038Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_rich_web_timeline_short_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.606656Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_rich_web_timeline_short_options` because it could not be opened.
2025-06-10T12:22:22.607279Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.607539Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.607831Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.608440Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_rich_web_timeline_style_options.ibd' OS error: 103
2025-06-10T12:22:22.608997Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.609334Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.609757Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_rich_web_timeline_style_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.610529Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_rich_web_timeline_style_options` because it could not be opened.
2025-06-10T12:22:22.611078Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.611421Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.611698Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.612121Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_rich_web_timeline_style_options_2.ibd' OS error: 103
2025-06-10T12:22:22.612519Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.612801Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.613347Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_rich_web_timeline_style_options_2`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.614011Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_rich_web_timeline_style_options_2` because it could not be opened.
2025-06-10T12:22:22.614513Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.614766Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.615112Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.615499Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_sbi_instagram_feed_locator.ibd' OS error: 103
2025-06-10T12:22:22.615935Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.616246Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.616784Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_sbi_instagram_feed_locator`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.618152Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_sbi_instagram_feed_locator` because it could not be opened.
2025-06-10T12:22:22.619397Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.619709Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.619994Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.620395Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_sbi_instagram_feeds_posts.ibd' OS error: 103
2025-06-10T12:22:22.620812Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.621081Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.621503Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_sbi_instagram_feeds_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.622162Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_sbi_instagram_feeds_posts` because it could not be opened.
2025-06-10T12:22:22.622681Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.622988Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.623271Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.623739Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_sbi_instagram_posts.ibd' OS error: 103
2025-06-10T12:22:22.624114Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.624396Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.624900Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_sbi_instagram_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.625521Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_sbi_instagram_posts` because it could not be opened.
2025-06-10T12:22:22.626062Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.626352Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.626700Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.627119Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_sgpb_subscribers.ibd' OS error: 103
2025-06-10T12:22:22.627475Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.627784Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.628200Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_sgpb_subscribers`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.628821Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_sgpb_subscribers` because it could not be opened.
2025-06-10T12:22:22.629248Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.629517Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.629839Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.630229Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_sgpb_subscription_error_log.ibd' OS error: 103
2025-06-10T12:22:22.630635Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.630904Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.631318Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_sgpb_subscription_error_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.631969Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_sgpb_subscription_error_log` because it could not be opened.
2025-06-10T12:22:22.632397Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.632697Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.633039Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.633437Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:22.633835Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.634101Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.634511Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.635189Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:22.635688Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.635965Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.636303Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.636737Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:22.637079Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.637344Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.637802Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.638386Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:22.638854Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.639254Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.639516Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.639966Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:22.640298Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.640589Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.641006Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.641614Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_termmeta` because it could not be opened.
2025-06-10T12:22:22.642038Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.642304Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.642615Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.643076Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_terms.ibd' OS error: 103
2025-06-10T12:22:22.643466Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.643759Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.644248Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.644978Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_terms` because it could not be opened.
2025-06-10T12:22:22.645509Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.645833Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.646089Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.646457Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:22.646874Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.647130Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.648251Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.649979Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_usermeta` because it could not be opened.
2025-06-10T12:22:22.650621Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.650922Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.651361Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.651823Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_users.ibd' OS error: 103
2025-06-10T12:22:22.652181Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.652447Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.652864Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.653471Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_users` because it could not be opened.
2025-06-10T12:22:22.653889Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.654227Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.654580Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.654977Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_wc_admin_note_actions.ibd' OS error: 103
2025-06-10T12:22:22.655437Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.655712Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.656204Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_wc_admin_note_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.656927Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_wc_admin_note_actions` because it could not be opened.
2025-06-10T12:22:22.657763Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.658136Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.658426Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.658861Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_wc_admin_notes.ibd' OS error: 103
2025-06-10T12:22:22.659208Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.659470Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.659911Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_wc_admin_notes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.660490Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_wc_admin_notes` because it could not be opened.
2025-06-10T12:22:22.660943Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.661211Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.661482Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.661896Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_wc_category_lookup.ibd' OS error: 103
2025-06-10T12:22:22.662248Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.662509Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.662951Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_wc_category_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.663539Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_wc_category_lookup` because it could not be opened.
2025-06-10T12:22:22.663970Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.664233Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.664503Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.665071Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_wc_customer_lookup.ibd' OS error: 103
2025-06-10T12:22:22.665424Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.665717Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.666128Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_wc_customer_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.666791Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_wc_customer_lookup` because it could not be opened.
2025-06-10T12:22:22.667263Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.667530Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.667844Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.668225Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_wc_download_log.ibd' OS error: 103
2025-06-10T12:22:22.668577Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.668891Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.669397Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_wc_download_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.670110Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_wc_download_log` because it could not be opened.
2025-06-10T12:22:22.670535Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.670899Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.671161Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.671558Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_wc_order_coupon_lookup.ibd' OS error: 103
2025-06-10T12:22:22.671965Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.672221Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.672672Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_wc_order_coupon_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.673277Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_wc_order_coupon_lookup` because it could not be opened.
2025-06-10T12:22:22.673863Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.674252Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.674703Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.675329Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_wc_order_product_lookup.ibd' OS error: 103
2025-06-10T12:22:22.675928Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.676313Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.677078Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_wc_order_product_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.677846Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_wc_order_product_lookup` because it could not be opened.
2025-06-10T12:22:22.678312Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.678619Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.678903Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.679353Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_wc_order_stats.ibd' OS error: 103
2025-06-10T12:22:22.679804Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.680066Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.680476Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_wc_order_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.681156Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_wc_order_stats` because it could not be opened.
2025-06-10T12:22:22.681630Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.682378Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.682649Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.683698Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_wc_order_tax_lookup.ibd' OS error: 103
2025-06-10T12:22:22.684082Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.684351Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.684781Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_wc_order_tax_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.685373Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_wc_order_tax_lookup` because it could not be opened.
2025-06-10T12:22:22.685938Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.686203Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.686537Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.686946Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_wc_product_meta_lookup.ibd' OS error: 103
2025-06-10T12:22:22.687295Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.687671Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.688084Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_wc_product_meta_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.688873Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_wc_product_meta_lookup` because it could not be opened.
2025-06-10T12:22:22.689752Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.690342Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.690798Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.691207Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_wc_reserved_stock.ibd' OS error: 103
2025-06-10T12:22:22.691653Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.692009Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.692457Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_wc_reserved_stock`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.693079Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_wc_reserved_stock` because it could not be opened.
2025-06-10T12:22:22.693560Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.693827Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.694187Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.694730Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_wc_tax_rate_classes.ibd' OS error: 103
2025-06-10T12:22:22.695090Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.695345Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.695834Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_wc_tax_rate_classes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.696422Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_wc_tax_rate_classes` because it could not be opened.
2025-06-10T12:22:22.696905Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.697158Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.697499Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.697942Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_wc_webhooks.ibd' OS error: 103
2025-06-10T12:22:22.698263Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.698567Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.698963Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_wc_webhooks`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.699607Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_wc_webhooks` because it could not be opened.
2025-06-10T12:22:22.699994Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.700374Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.700796Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.701201Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_woocommerce_api_keys.ibd' OS error: 103
2025-06-10T12:22:22.701597Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.701848Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.702243Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_woocommerce_api_keys`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.702935Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_woocommerce_api_keys` because it could not be opened.
2025-06-10T12:22:22.703425Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.703702Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.703958Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.704322Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_woocommerce_attribute_taxonomies.ibd' OS error: 103
2025-06-10T12:22:22.704775Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.705026Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.705523Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_woocommerce_attribute_taxonomies`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.706198Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_woocommerce_attribute_taxonomies` because it could not be opened.
2025-06-10T12:22:22.706949Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.707218Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.707579Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.707949Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_woocommerce_downloadable_product_permissions.ibd' OS error: 103
2025-06-10T12:22:22.708504Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.708799Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.709227Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_woocommerce_downloadable_product_permissions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.709961Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_woocommerce_downloadable_product_permissions` because it could not be opened.
2025-06-10T12:22:22.710517Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.710781Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.711036Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.711569Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_woocommerce_log.ibd' OS error: 103
2025-06-10T12:22:22.712081Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.712400Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.712970Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_woocommerce_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.713956Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_woocommerce_log` because it could not be opened.
2025-06-10T12:22:22.714696Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.714978Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.715255Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.715701Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_woocommerce_order_itemmeta.ibd' OS error: 103
2025-06-10T12:22:22.716071Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.716338Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.716871Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_woocommerce_order_itemmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.717590Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_woocommerce_order_itemmeta` because it could not be opened.
2025-06-10T12:22:22.718017Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.718269Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.718679Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.719064Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_woocommerce_order_items.ibd' OS error: 103
2025-06-10T12:22:22.719503Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.719850Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.720255Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_woocommerce_order_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.721424Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_woocommerce_order_items` because it could not be opened.
2025-06-10T12:22:22.722143Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.722466Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.722768Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.723144Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_woocommerce_payment_tokenmeta.ibd' OS error: 103
2025-06-10T12:22:22.723621Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.723878Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.724280Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_woocommerce_payment_tokenmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.724929Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_woocommerce_payment_tokenmeta` because it could not be opened.
2025-06-10T12:22:22.725360Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.725804Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.726114Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.726543Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_woocommerce_payment_tokens.ibd' OS error: 103
2025-06-10T12:22:22.726900Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.727152Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.727777Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_woocommerce_payment_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.728344Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_woocommerce_payment_tokens` because it could not be opened.
2025-06-10T12:22:22.728995Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.729357Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.729752Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.730112Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_woocommerce_sessions.ibd' OS error: 103
2025-06-10T12:22:22.730630Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.731009Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.731727Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_woocommerce_sessions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.732714Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_woocommerce_sessions` because it could not be opened.
2025-06-10T12:22:22.733692Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.734066Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.734591Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.735227Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_woocommerce_shipping_zone_locations.ibd' OS error: 103
2025-06-10T12:22:22.735752Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.736018Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.736491Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_woocommerce_shipping_zone_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.737118Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_woocommerce_shipping_zone_locations` because it could not be opened.
2025-06-10T12:22:22.737654Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.737922Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.738197Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.738652Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_woocommerce_shipping_zone_methods.ibd' OS error: 103
2025-06-10T12:22:22.739036Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.739296Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.739768Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_woocommerce_shipping_zone_methods`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.740523Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_woocommerce_shipping_zone_methods` because it could not be opened.
2025-06-10T12:22:22.740999Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.741252Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.741597Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.742261Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_woocommerce_shipping_zones.ibd' OS error: 103
2025-06-10T12:22:22.742704Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.742976Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.743533Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_woocommerce_shipping_zones`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.744196Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_woocommerce_shipping_zones` because it could not be opened.
2025-06-10T12:22:22.744871Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.745673Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.745936Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.746370Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_woocommerce_tax_rate_locations.ibd' OS error: 103
2025-06-10T12:22:22.746821Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.747117Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.747542Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_woocommerce_tax_rate_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.748219Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_woocommerce_tax_rate_locations` because it could not be opened.
2025-06-10T12:22:22.748828Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.749240Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.749558Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.750042Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_woocommerce_tax_rates.ibd' OS error: 103
2025-06-10T12:22:22.750388Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.750699Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.751177Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_woocommerce_tax_rates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.751943Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_woocommerce_tax_rates` because it could not be opened.
2025-06-10T12:22:22.752417Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.752759Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.753024Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.753399Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_wpgmza.ibd' OS error: 103
2025-06-10T12:22:22.753852Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.754124Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.754633Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_wpgmza`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.755196Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_wpgmza` because it could not be opened.
2025-06-10T12:22:22.755601Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.755965Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.756273Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.756738Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_wpgmza_circles.ibd' OS error: 103
2025-06-10T12:22:22.757138Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.757399Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.758006Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_wpgmza_circles`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.758597Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_wpgmza_circles` because it could not be opened.
2025-06-10T12:22:22.759007Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.759257Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.759514Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.759968Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_wpgmza_maps.ibd' OS error: 103
2025-06-10T12:22:22.760287Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.760536Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.761023Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_wpgmza_maps`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.761582Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_wpgmza_maps` because it could not be opened.
2025-06-10T12:22:22.761984Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.762236Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.762491Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.762986Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_wpgmza_polygon.ibd' OS error: 103
2025-06-10T12:22:22.763314Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.763597Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.764086Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_wpgmza_polygon`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.764771Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_wpgmza_polygon` because it could not be opened.
2025-06-10T12:22:22.765161Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.765416Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.765738Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.766172Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_wpgmza_polylines.ibd' OS error: 103
2025-06-10T12:22:22.766616Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.766898Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.767297Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_wpgmza_polylines`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.767961Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_wpgmza_polylines` because it could not be opened.
2025-06-10T12:22:22.768363Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.768693Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.768984Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.769340Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_wpgmza_rectangles.ibd' OS error: 103
2025-06-10T12:22:22.769761Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.770010Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.770404Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_wpgmza_rectangles`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.771029Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_wpgmza_rectangles` because it could not be opened.
2025-06-10T12:22:22.771424Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.771763Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.772073Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.772491Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:22.772988Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.773260Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.773785Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.774384Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:22.774917Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.775172Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.775615Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.775987Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:22.776846Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.777102Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.777592Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.778749Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:22.779665Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.779994Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.780286Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.780681Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:22.781066Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.781328Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.781779Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.782537Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:22.783081Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.783353Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.783622Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.784084Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem30\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:22.784433Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.784693Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.785238Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem30/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.785828Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem30/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:22.786383Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.786638Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.786988Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.787364Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem4\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:22.787775Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.788135Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.788533Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem4/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.789200Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem4/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:22.789584Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.789899Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.790183Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.790547Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem4\wp_comments.ibd' OS error: 103
2025-06-10T12:22:22.790952Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.791299Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.791810Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem4/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.792530Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem4/wp_comments` because it could not be opened.
2025-06-10T12:22:22.793036Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.793289Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.793558Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.793986Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem4\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:22.794299Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.794550Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.795381Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem4/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.796044Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem4/wp_fbv` because it could not be opened.
2025-06-10T12:22:22.796421Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.796672Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.797036Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.797396Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem4\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:22.797726Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.798044Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.798429Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem4/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.799280Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem4/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:22.799663Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.800078Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.800490Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.800970Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem4\wp_gg_attributes.ibd' OS error: 103
2025-06-10T12:22:22.801293Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.801542Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.802127Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem4/wp_gg_attributes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.802701Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem4/wp_gg_attributes` because it could not be opened.
2025-06-10T12:22:22.803248Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.803514Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.803824Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.804210Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem4\wp_gg_cdn.ibd' OS error: 103
2025-06-10T12:22:22.804532Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.804822Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.805284Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem4/wp_gg_cdn`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.805877Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem4/wp_gg_cdn` because it could not be opened.
2025-06-10T12:22:22.806244Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.806509Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.806845Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.807242Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem4\wp_gg_folders.ibd' OS error: 103
2025-06-10T12:22:22.807570Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.807868Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.808283Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem4/wp_gg_folders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.808938Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem4/wp_gg_folders` because it could not be opened.
2025-06-10T12:22:22.809318Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.809580Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.809922Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.810308Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem4\wp_gg_galleries.ibd' OS error: 103
2025-06-10T12:22:22.810641Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.811032Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.811523Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem4/wp_gg_galleries`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.812131Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem4/wp_gg_galleries` because it could not be opened.
2025-06-10T12:22:22.812523Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.812829Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.813103Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.813481Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem4\wp_gg_galleries_excluded.ibd' OS error: 103
2025-06-10T12:22:22.813874Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.814465Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.814922Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem4/wp_gg_galleries_excluded`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.815517Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem4/wp_gg_galleries_excluded` because it could not be opened.
2025-06-10T12:22:22.816252Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.816562Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.816873Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.817263Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem4\wp_gg_galleries_resources.ibd' OS error: 103
2025-06-10T12:22:22.817618Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.817934Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.818388Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem4/wp_gg_galleries_resources`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.819021Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem4/wp_gg_galleries_resources` because it could not be opened.
2025-06-10T12:22:22.819467Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.819757Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.820070Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.820516Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem4\wp_gg_image_optimize.ibd' OS error: 103
2025-06-10T12:22:22.820947Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.821211Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.821629Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem4/wp_gg_image_optimize`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.822263Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem4/wp_gg_image_optimize` because it could not be opened.
2025-06-10T12:22:22.822694Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.823007Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.823279Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.823790Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem4\wp_gg_membership_presets.ibd' OS error: 103
2025-06-10T12:22:22.824151Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.824435Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.824965Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem4/wp_gg_membership_presets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.826033Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem4/wp_gg_membership_presets` because it could not be opened.
2025-06-10T12:22:22.826798Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.827076Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.827367Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.827768Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem4\wp_gg_photos.ibd' OS error: 103
2025-06-10T12:22:22.828079Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.828330Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.828855Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem4/wp_gg_photos`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.829525Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem4/wp_gg_photos` because it could not be opened.
2025-06-10T12:22:22.829931Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.830187Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.830541Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.830914Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem4\wp_gg_photos_pos.ibd' OS error: 103
2025-06-10T12:22:22.831241Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.831635Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.832034Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem4/wp_gg_photos_pos`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.832724Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem4/wp_gg_photos_pos` because it could not be opened.
2025-06-10T12:22:22.833316Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.833650Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.833999Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.834431Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem4\wp_gg_photos_settings.ibd' OS error: 103
2025-06-10T12:22:22.834794Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.835065Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.835554Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem4/wp_gg_photos_settings`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.836141Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem4/wp_gg_photos_settings` because it could not be opened.
2025-06-10T12:22:22.836647Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.836904Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.837161Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.837653Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem4\wp_gg_settings_presets.ibd' OS error: 103
2025-06-10T12:22:22.838052Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.838304Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.838755Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem4/wp_gg_settings_presets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.839612Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem4/wp_gg_settings_presets` because it could not be opened.
2025-06-10T12:22:22.840028Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.840276Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.840635Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.840999Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem4\wp_gg_settings_sets.ibd' OS error: 103
2025-06-10T12:22:22.841415Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.841950Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.842501Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem4/wp_gg_settings_sets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.843538Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem4/wp_gg_settings_sets` because it could not be opened.
2025-06-10T12:22:22.843952Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.844260Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.844608Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.844990Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem4\wp_gg_stats.ibd' OS error: 103
2025-06-10T12:22:22.845356Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.845636Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.846038Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem4/wp_gg_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.846723Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem4/wp_gg_stats` because it could not be opened.
2025-06-10T12:22:22.847120Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.847448Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.847732Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.848120Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem4\wp_gg_tags.ibd' OS error: 103
2025-06-10T12:22:22.848522Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.848788Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.849203Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem4/wp_gg_tags`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.849838Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem4/wp_gg_tags` because it could not be opened.
2025-06-10T12:22:22.850231Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.850574Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.850837Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.851206Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem4\wp_links.ibd' OS error: 103
2025-06-10T12:22:22.851611Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.851865Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.852335Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem4/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.853003Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem4/wp_links` because it could not be opened.
2025-06-10T12:22:22.853593Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.853912Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.854168Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.854582Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem4\wp_newsletter.ibd' OS error: 103
2025-06-10T12:22:22.854906Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.855159Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.856371Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem4/wp_newsletter`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.857113Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem4/wp_newsletter` because it could not be opened.
2025-06-10T12:22:22.857608Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.857914Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.858246Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.858704Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem4\wp_newsletter_emails.ibd' OS error: 103
2025-06-10T12:22:22.859106Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.859399Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.859822Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem4/wp_newsletter_emails`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.860483Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem4/wp_newsletter_emails` because it could not be opened.
2025-06-10T12:22:22.860960Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.861289Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.861563Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.861952Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem4\wp_newsletter_sent.ibd' OS error: 103
2025-06-10T12:22:22.862514Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.862959Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.863602Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem4/wp_newsletter_sent`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.864250Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem4/wp_newsletter_sent` because it could not be opened.
2025-06-10T12:22:22.864739Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.865005Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.865336Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.865705Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem4\wp_newsletter_stats.ibd' OS error: 103
2025-06-10T12:22:22.866110Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.866456Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.866995Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem4/wp_newsletter_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.867646Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem4/wp_newsletter_stats` because it could not be opened.
2025-06-10T12:22:22.868060Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.868357Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.868615Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.868977Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem4\wp_newsletter_user_logs.ibd' OS error: 103
2025-06-10T12:22:22.869374Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.869623Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.870044Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem4/wp_newsletter_user_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.870657Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem4/wp_newsletter_user_logs` because it could not be opened.
2025-06-10T12:22:22.871046Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.871421Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.871757Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.872135Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem4\wp_options.ibd' OS error: 103
2025-06-10T12:22:22.872515Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.872755Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.873173Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem4/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.874310Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem4/wp_options` because it could not be opened.
2025-06-10T12:22:22.874725Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.875069Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.875492Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.875853Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem4\wp_post_views.ibd' OS error: 103
2025-06-10T12:22:22.876269Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.876647Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.877032Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem4/wp_post_views`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.877676Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem4/wp_post_views` because it could not be opened.
2025-06-10T12:22:22.878044Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.878443Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.878836Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.879374Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem4\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:22.879694Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.879947Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.880433Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem4/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.880982Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem4/wp_postmeta` because it could not be opened.
2025-06-10T12:22:22.881439Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.881694Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.881954Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.882374Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem4\wp_posts.ibd' OS error: 103
2025-06-10T12:22:22.882698Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.882999Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.883501Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem4/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.884064Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem4/wp_posts` because it could not be opened.
2025-06-10T12:22:22.884525Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.884793Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.885068Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.885483Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem4\wp_revslider_css.ibd' OS error: 103
2025-06-10T12:22:22.885825Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.886117Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.886555Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem4/wp_revslider_css`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.887313Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem4/wp_revslider_css` because it could not be opened.
2025-06-10T12:22:22.887760Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.888019Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.888416Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.888996Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem4\wp_revslider_css_bkp.ibd' OS error: 103
2025-06-10T12:22:22.889846Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.890099Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.890627Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem4/wp_revslider_css_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.891227Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem4/wp_revslider_css_bkp` because it could not be opened.
2025-06-10T12:22:22.891810Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.892088Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.892401Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.892848Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem4\wp_revslider_layer_animations.ibd' OS error: 103
2025-06-10T12:22:22.893221Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.893549Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.894017Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem4/wp_revslider_layer_animations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.894747Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem4/wp_revslider_layer_animations` because it could not be opened.
2025-06-10T12:22:22.895273Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.895559Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.895833Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.896227Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem4\wp_revslider_layer_animations_bkp.ibd' OS error: 103
2025-06-10T12:22:22.896743Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.897015Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.897604Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem4/wp_revslider_layer_animations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.898333Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem4/wp_revslider_layer_animations_bkp` because it could not be opened.
2025-06-10T12:22:22.898913Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.899196Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.899564Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.899971Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem4\wp_revslider_navigations.ibd' OS error: 103
2025-06-10T12:22:22.900342Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.900703Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.901257Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem4/wp_revslider_navigations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.902047Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem4/wp_revslider_navigations` because it could not be opened.
2025-06-10T12:22:22.902773Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.903047Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.903309Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.903770Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem4\wp_revslider_navigations_bkp.ibd' OS error: 103
2025-06-10T12:22:22.904112Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.904434Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.905063Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem4/wp_revslider_navigations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.905877Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem4/wp_revslider_navigations_bkp` because it could not be opened.
2025-06-10T12:22:22.906311Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.906659Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.906922Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.907299Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem4\wp_revslider_sliders.ibd' OS error: 103
2025-06-10T12:22:22.907700Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.907966Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.908471Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem4/wp_revslider_sliders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.909049Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem4/wp_revslider_sliders` because it could not be opened.
2025-06-10T12:22:22.909616Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.909891Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.910159Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.910595Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem4\wp_revslider_sliders_bkp.ibd' OS error: 103
2025-06-10T12:22:22.910940Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.911239Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.911762Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem4/wp_revslider_sliders_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.912368Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem4/wp_revslider_sliders_bkp` because it could not be opened.
2025-06-10T12:22:22.912782Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.913036Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.913301Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.913751Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem4\wp_revslider_slides.ibd' OS error: 103
2025-06-10T12:22:22.914093Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.914438Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.914857Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem4/wp_revslider_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.915528Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem4/wp_revslider_slides` because it could not be opened.
2025-06-10T12:22:22.916240Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.916826Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.917206Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.917705Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem4\wp_revslider_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:22.918046Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.918326Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.918753Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem4/wp_revslider_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.920083Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem4/wp_revslider_slides_bkp` because it could not be opened.
2025-06-10T12:22:22.921845Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.922444Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.922826Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.923275Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem4\wp_revslider_static_slides.ibd' OS error: 103
2025-06-10T12:22:22.923680Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.923956Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.924421Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem4/wp_revslider_static_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.925271Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem4/wp_revslider_static_slides` because it could not be opened.
2025-06-10T12:22:22.925957Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.926408Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.926821Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.927487Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem4\wp_revslider_static_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:22.928020Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.928526Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.929141Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem4/wp_revslider_static_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.930189Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem4/wp_revslider_static_slides_bkp` because it could not be opened.
2025-06-10T12:22:22.931034Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.931507Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.931892Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.932477Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem4\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:22.932984Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.933394Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.933825Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem4/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.934481Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem4/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:22.934906Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.935172Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.935511Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.935899Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem4\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:22.936234Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.936558Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.936968Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem4/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.937602Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem4/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:22.938024Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.938360Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.938633Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.939000Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem4\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:22.939445Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.939783Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.940175Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem4/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.940800Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem4/wp_termmeta` because it could not be opened.
2025-06-10T12:22:22.941215Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.941594Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.941850Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.942215Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem4\wp_terms.ibd' OS error: 103
2025-06-10T12:22:22.942657Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.942905Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.943422Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem4/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.943953Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem4/wp_terms` because it could not be opened.
2025-06-10T12:22:22.944398Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.944655Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.944914Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.945397Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem4\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:22.945753Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.946003Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.946500Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem4/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.947040Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem4/wp_usermeta` because it could not be opened.
2025-06-10T12:22:22.947572Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.947972Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.948279Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.948746Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem4\wp_users.ibd' OS error: 103
2025-06-10T12:22:22.949295Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.949653Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.950052Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem4/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.950669Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem4/wp_users` because it could not be opened.
2025-06-10T12:22:22.951194Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.951918Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.952214Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.952733Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem4\wp_wpfm_backup.ibd' OS error: 103
2025-06-10T12:22:22.953264Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.954077Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.954525Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem4/wp_wpfm_backup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.955249Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem4/wp_wpfm_backup` because it could not be opened.
2025-06-10T12:22:22.955813Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.956088Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.956363Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.956790Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem4\wp_yoast_seo_links.ibd' OS error: 103
2025-06-10T12:22:22.957139Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.957405Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.957850Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem4/wp_yoast_seo_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.958442Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem4/wp_yoast_seo_links` because it could not be opened.
2025-06-10T12:22:22.958924Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.959198Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.959477Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.959939Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem4\wp_yoast_seo_meta.ibd' OS error: 103
2025-06-10T12:22:22.960403Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.960715Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.961159Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem4/wp_yoast_seo_meta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.961810Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem4/wp_yoast_seo_meta` because it could not be opened.
2025-06-10T12:22:22.962694Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.963006Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.963274Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.963722Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_actionscheduler_actions.ibd' OS error: 103
2025-06-10T12:22:22.964071Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.964323Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.964822Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_actionscheduler_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.965399Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_actionscheduler_actions` because it could not be opened.
2025-06-10T12:22:22.965872Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.966238Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.966586Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.967038Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_actionscheduler_claims.ibd' OS error: 103
2025-06-10T12:22:22.967388Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.967729Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.968124Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_actionscheduler_claims`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.968761Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_actionscheduler_claims` because it could not be opened.
2025-06-10T12:22:22.969170Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.969427Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.969761Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.970122Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_actionscheduler_groups.ibd' OS error: 103
2025-06-10T12:22:22.970602Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.970874Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.971270Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_actionscheduler_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.971906Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_actionscheduler_groups` because it could not be opened.
2025-06-10T12:22:22.972288Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.972597Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.972870Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.973250Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_actionscheduler_logs.ibd' OS error: 103
2025-06-10T12:22:22.973714Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.974001Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.974395Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_actionscheduler_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.975092Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_actionscheduler_logs` because it could not be opened.
2025-06-10T12:22:22.975519Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.975799Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.976058Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.976424Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_cf7_vdata.ibd' OS error: 103
2025-06-10T12:22:22.976826Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.977077Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.977505Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_cf7_vdata`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.978419Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_cf7_vdata` because it could not be opened.
2025-06-10T12:22:22.979559Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.979850Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.980127Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.980543Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_cf7_vdata_entry.ibd' OS error: 103
2025-06-10T12:22:22.980903Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.981169Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.981635Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_cf7_vdata_entry`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.982213Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_cf7_vdata_entry` because it could not be opened.
2025-06-10T12:22:22.982752Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.983029Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.983300Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.983709Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:22.984066Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.984330Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.984997Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.985884Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:22.986712Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.987113Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.987518Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.988019Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_comments.ibd' OS error: 103
2025-06-10T12:22:22.988350Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.988635Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.989101Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.989636Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_comments` because it could not be opened.
2025-06-10T12:22:22.990108Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.990504Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.990831Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.991505Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_csshero4.ibd' OS error: 103
2025-06-10T12:22:22.992019Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.992519Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.993171Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_csshero4`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.994077Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_csshero4` because it could not be opened.
2025-06-10T12:22:22.994706Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.995027Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.995527Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.996109Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_db7_forms.ibd' OS error: 103
2025-06-10T12:22:22.996502Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:22.996800Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:22.997249Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_db7_forms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:22.997987Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_db7_forms` because it could not be opened.
2025-06-10T12:22:22.998568Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:22.998875Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:22.999156Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:22.999642Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:23.000109Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.000398Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.001006Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.001677Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_fbv` because it could not be opened.
2025-06-10T12:22:23.002105Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.002407Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.002697Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.003095Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:23.003514Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.003782Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.004199Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.004824Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:23.005265Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.005603Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.005883Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.006266Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_gg_attributes.ibd' OS error: 103
2025-06-10T12:22:23.006635Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.006899Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.007369Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_gg_attributes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.008067Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_gg_attributes` because it could not be opened.
2025-06-10T12:22:23.008528Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.008797Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.009058Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.009524Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_gg_cdn.ibd' OS error: 103
2025-06-10T12:22:23.009838Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.010089Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.010639Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_gg_cdn`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.011274Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_gg_cdn` because it could not be opened.
2025-06-10T12:22:23.011700Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.011957Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.012223Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.012667Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_gg_folders.ibd' OS error: 103
2025-06-10T12:22:23.013007Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.013559Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.014068Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_gg_folders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.014711Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_gg_folders` because it could not be opened.
2025-06-10T12:22:23.015124Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.015433Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.016017Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.016489Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_gg_galleries.ibd' OS error: 103
2025-06-10T12:22:23.017038Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.017401Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.017971Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_gg_galleries`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.018652Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_gg_galleries` because it could not be opened.
2025-06-10T12:22:23.019119Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.019406Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.019698Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.020086Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_gg_galleries_excluded.ibd' OS error: 103
2025-06-10T12:22:23.020827Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.021113Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.021562Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_gg_galleries_excluded`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.022136Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_gg_galleries_excluded` because it could not be opened.
2025-06-10T12:22:23.022726Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.023010Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.023306Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.023699Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_gg_galleries_resources.ibd' OS error: 103
2025-06-10T12:22:23.024066Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.024387Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.024812Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_gg_galleries_resources`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.025466Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_gg_galleries_resources` because it could not be opened.
2025-06-10T12:22:23.025919Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.026245Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.026519Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.026909Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_gg_image_optimize.ibd' OS error: 103
2025-06-10T12:22:23.027296Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.027626Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.028063Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_gg_image_optimize`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.028771Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_gg_image_optimize` because it could not be opened.
2025-06-10T12:22:23.029330Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.029677Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.029975Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.030440Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_gg_membership_presets.ibd' OS error: 103
2025-06-10T12:22:23.030852Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.031212Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.031621Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_gg_membership_presets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.032285Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_gg_membership_presets` because it could not be opened.
2025-06-10T12:22:23.032731Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.033000Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.033298Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.033680Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_gg_photos.ibd' OS error: 103
2025-06-10T12:22:23.034140Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.034413Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.034822Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_gg_photos`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.035429Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_gg_photos` because it could not be opened.
2025-06-10T12:22:23.035812Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.036076Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.036471Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.036926Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_gg_photos_pos.ibd' OS error: 103
2025-06-10T12:22:23.037307Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.037574Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.037987Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_gg_photos_pos`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.038621Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_gg_photos_pos` because it could not be opened.
2025-06-10T12:22:23.039034Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.039345Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.039603Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.040126Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_gg_photos_settings.ibd' OS error: 103
2025-06-10T12:22:23.040602Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.040865Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.041347Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_gg_photos_settings`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.041901Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_gg_photos_settings` because it could not be opened.
2025-06-10T12:22:23.042400Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.042674Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.042929Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.043373Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_gg_settings_presets.ibd' OS error: 103
2025-06-10T12:22:23.043710Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.043957Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.044428Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_gg_settings_presets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.045006Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_gg_settings_presets` because it could not be opened.
2025-06-10T12:22:23.045475Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.045726Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.046233Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.046626Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_gg_settings_sets.ibd' OS error: 103
2025-06-10T12:22:23.046965Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.047331Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.047750Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_gg_settings_sets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.048395Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_gg_settings_sets` because it could not be opened.
2025-06-10T12:22:23.048797Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.049150Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.049436Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.049803Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_gg_stats.ibd' OS error: 103
2025-06-10T12:22:23.050211Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.050458Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.050855Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_gg_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.051492Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_gg_stats` because it could not be opened.
2025-06-10T12:22:23.052023Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.052348Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.052604Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.052965Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_gg_tags.ibd' OS error: 103
2025-06-10T12:22:23.053407Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.053654Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.054041Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_gg_tags`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.054747Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_gg_tags` because it could not be opened.
2025-06-10T12:22:23.055184Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.055450Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.055705Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.056072Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_links.ibd' OS error: 103
2025-06-10T12:22:23.056479Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.056725Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.057210Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.057749Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_links` because it could not be opened.
2025-06-10T12:22:23.058224Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.058492Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.058764Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.059210Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_options.ibd' OS error: 103
2025-06-10T12:22:23.059540Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.059854Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.060362Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.060986Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_options` because it could not be opened.
2025-06-10T12:22:23.061471Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.061766Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.062109Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.062664Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_post_views.ibd' OS error: 103
2025-06-10T12:22:23.063009Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.063304Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.063775Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_post_views`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.065226Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_post_views` because it could not be opened.
2025-06-10T12:22:23.065685Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.066425Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.066704Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.067124Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:23.067487Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.067751Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.068167Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.068773Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_postmeta` because it could not be opened.
2025-06-10T12:22:23.069181Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.069477Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.069754Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.070145Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_posts.ibd' OS error: 103
2025-06-10T12:22:23.070507Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.070779Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.071203Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.071831Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_posts` because it could not be opened.
2025-06-10T12:22:23.072450Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.072756Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.073043Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.073472Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_redirection_404.ibd' OS error: 103
2025-06-10T12:22:23.073837Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.074097Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.074532Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_redirection_404`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.075111Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_redirection_404` because it could not be opened.
2025-06-10T12:22:23.075587Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.075920Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.076228Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.076741Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_redirection_groups.ibd' OS error: 103
2025-06-10T12:22:23.077098Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.077439Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.077877Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_redirection_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.078526Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_redirection_groups` because it could not be opened.
2025-06-10T12:22:23.079039Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.079372Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.079647Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.080030Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_redirection_items.ibd' OS error: 103
2025-06-10T12:22:23.080429Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.080690Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.081100Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_redirection_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.081752Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_redirection_items` because it could not be opened.
2025-06-10T12:22:23.082159Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.082469Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.082784Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.083205Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_redirection_logs.ibd' OS error: 103
2025-06-10T12:22:23.083595Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.083867Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.084302Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_redirection_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.084911Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_redirection_logs` because it could not be opened.
2025-06-10T12:22:23.085355Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.085632Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.085897Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.086269Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_revslider_css.ibd' OS error: 103
2025-06-10T12:22:23.086659Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.086910Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.087345Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_revslider_css`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.087973Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_revslider_css` because it could not be opened.
2025-06-10T12:22:23.088692Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.088958Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.089222Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.089767Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_revslider_css_bkp.ibd' OS error: 103
2025-06-10T12:22:23.090108Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.090429Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.090853Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_revslider_css_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.091492Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_revslider_css_bkp` because it could not be opened.
2025-06-10T12:22:23.091920Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.092197Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.092562Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.092953Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_revslider_layer_animations.ibd' OS error: 103
2025-06-10T12:22:23.093370Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.093652Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.094075Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_revslider_layer_animations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.094722Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_revslider_layer_animations` because it could not be opened.
2025-06-10T12:22:23.095170Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.096038Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.096452Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.096876Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_revslider_layer_animations_bkp.ibd' OS error: 103
2025-06-10T12:22:23.097344Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.097623Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.098136Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_revslider_layer_animations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.098797Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_revslider_layer_animations_bkp` because it could not be opened.
2025-06-10T12:22:23.099298Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.099580Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.099864Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.100271Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_revslider_navigations.ibd' OS error: 103
2025-06-10T12:22:23.100705Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.100969Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.101446Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_revslider_navigations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.102111Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_revslider_navigations` because it could not be opened.
2025-06-10T12:22:23.102613Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.102888Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.103299Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.103708Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_revslider_navigations_bkp.ibd' OS error: 103
2025-06-10T12:22:23.104135Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.104398Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.104872Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_revslider_navigations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.105681Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_revslider_navigations_bkp` because it could not be opened.
2025-06-10T12:22:23.106282Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.106549Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.106812Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.107248Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_revslider_sliders.ibd' OS error: 103
2025-06-10T12:22:23.107622Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.107873Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.108369Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_revslider_sliders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.108926Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_revslider_sliders` because it could not be opened.
2025-06-10T12:22:23.109387Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.109644Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.109905Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.110465Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_revslider_sliders_bkp.ibd' OS error: 103
2025-06-10T12:22:23.110821Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.111147Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.111562Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_revslider_sliders_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.112251Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_revslider_sliders_bkp` because it could not be opened.
2025-06-10T12:22:23.112660Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.112915Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.113279Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.113644Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_revslider_slides.ibd' OS error: 103
2025-06-10T12:22:23.114082Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.114352Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.114741Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_revslider_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.115391Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_revslider_slides` because it could not be opened.
2025-06-10T12:22:23.115764Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.116110Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.116560Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.116988Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_revslider_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:23.117358Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.117623Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.118105Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_revslider_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.118691Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_revslider_slides_bkp` because it could not be opened.
2025-06-10T12:22:23.119174Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.119428Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.119706Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.120153Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_revslider_static_slides.ibd' OS error: 103
2025-06-10T12:22:23.120517Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.120781Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.121257Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_revslider_static_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.121850Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_revslider_static_slides` because it could not be opened.
2025-06-10T12:22:23.122579Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.122859Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.123178Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.123561Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_revslider_static_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:23.123944Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.124359Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.124810Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_revslider_static_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.125530Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_revslider_static_slides_bkp` because it could not be opened.
2025-06-10T12:22:23.126083Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.126519Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.126785Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.127283Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_rich_web_icons.ibd' OS error: 103
2025-06-10T12:22:23.127612Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.127989Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.128413Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_rich_web_icons`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.129233Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_rich_web_icons` because it could not be opened.
2025-06-10T12:22:23.129754Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.130046Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.130428Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.130825Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_rich_web_timeline_manager.ibd' OS error: 103
2025-06-10T12:22:23.131209Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.131532Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.131964Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_rich_web_timeline_manager`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.132566Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_rich_web_timeline_manager` because it could not be opened.
2025-06-10T12:22:23.133085Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.133353Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.133625Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.134071Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_rich_web_timeline_options.ibd' OS error: 103
2025-06-10T12:22:23.134444Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.134708Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.135461Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_rich_web_timeline_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.136136Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_rich_web_timeline_options` because it could not be opened.
2025-06-10T12:22:23.136619Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.136979Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.137294Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.137692Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_rich_web_timeline_short_options.ibd' OS error: 103
2025-06-10T12:22:23.138197Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.138561Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.139087Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_rich_web_timeline_short_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.139789Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_rich_web_timeline_short_options` because it could not be opened.
2025-06-10T12:22:23.140355Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.140608Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.140961Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.141416Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_rich_web_timeline_style_options.ibd' OS error: 103
2025-06-10T12:22:23.141769Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.142165Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.142571Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_rich_web_timeline_style_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.143346Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_rich_web_timeline_style_options` because it could not be opened.
2025-06-10T12:22:23.143758Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.144125Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.144469Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.144868Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_rich_web_timeline_style_options_2.ibd' OS error: 103
2025-06-10T12:22:23.145255Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.145503Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.145991Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_rich_web_timeline_style_options_2`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.146575Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_rich_web_timeline_style_options_2` because it could not be opened.
2025-06-10T12:22:23.147080Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.147327Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.147581Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.148007Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_sbi_instagram_feed_locator.ibd' OS error: 103
2025-06-10T12:22:23.148350Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.148598Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.149157Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_sbi_instagram_feed_locator`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.150018Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_sbi_instagram_feed_locator` because it could not be opened.
2025-06-10T12:22:23.150429Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.150675Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.151032Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.151452Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_sbi_instagram_feeds_posts.ibd' OS error: 103
2025-06-10T12:22:23.151792Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.152135Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.152516Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_sbi_instagram_feeds_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.153172Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_sbi_instagram_feeds_posts` because it could not be opened.
2025-06-10T12:22:23.153555Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.153832Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.154206Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.154568Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_sbi_instagram_posts.ibd' OS error: 103
2025-06-10T12:22:23.155007Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.155262Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.155732Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_sbi_instagram_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.156333Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_sbi_instagram_posts` because it could not be opened.
2025-06-10T12:22:23.156830Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.157106Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.157365Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.157729Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_sgpb_subscribers.ibd' OS error: 103
2025-06-10T12:22:23.158163Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.158412Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.158838Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_sgpb_subscribers`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.159419Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_sgpb_subscribers` because it could not be opened.
2025-06-10T12:22:23.159870Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.160139Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.160468Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.160892Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_sgpb_subscription_error_log.ibd' OS error: 103
2025-06-10T12:22:23.161466Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.161713Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.162511Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_sgpb_subscription_error_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.163152Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_sgpb_subscription_error_log` because it could not be opened.
2025-06-10T12:22:23.163710Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.164008Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.164298Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.164677Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:23.165045Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.165307Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.165720Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.166338Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:23.166785Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.167094Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.167367Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.167755Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:23.168132Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.168396Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.168815Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.169500Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:23.169990Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.170420Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.170714Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.171125Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:23.171436Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.171681Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.172163Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.172725Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_termmeta` because it could not be opened.
2025-06-10T12:22:23.173143Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.173405Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.173674Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.174078Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_terms.ibd' OS error: 103
2025-06-10T12:22:23.174397Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.174833Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.175331Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.175882Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_terms` because it could not be opened.
2025-06-10T12:22:23.176300Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.176593Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.176881Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.177279Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:23.177584Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.177827Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.178434Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.179028Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_usermeta` because it could not be opened.
2025-06-10T12:22:23.179392Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.179638Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.179921Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.180499Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_users.ibd' OS error: 103
2025-06-10T12:22:23.180813Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.181304Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.181726Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.182357Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_users` because it could not be opened.
2025-06-10T12:22:23.182724Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.183072Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.183361Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.183720Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_wc_admin_note_actions.ibd' OS error: 103
2025-06-10T12:22:23.184140Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.184384Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.184766Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_wc_admin_note_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.185436Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_wc_admin_note_actions` because it could not be opened.
2025-06-10T12:22:23.185818Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.186155Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.186417Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.186784Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_wc_admin_notes.ibd' OS error: 103
2025-06-10T12:22:23.187193Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.187475Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.187980Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_wc_admin_notes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.188770Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_wc_admin_notes` because it could not be opened.
2025-06-10T12:22:23.189583Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.189899Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.190209Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.190648Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_wc_category_lookup.ibd' OS error: 103
2025-06-10T12:22:23.191062Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.191323Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.191706Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_wc_category_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.192497Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_wc_category_lookup` because it could not be opened.
2025-06-10T12:22:23.193374Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.193846Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.194625Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.195321Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_wc_customer_lookup.ibd' OS error: 103
2025-06-10T12:22:23.195711Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.195999Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.196418Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_wc_customer_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.197036Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_wc_customer_lookup` because it could not be opened.
2025-06-10T12:22:23.197485Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.197778Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.198091Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.198477Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_wc_download_log.ibd' OS error: 103
2025-06-10T12:22:23.198855Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.199121Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.199541Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_wc_download_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.200188Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_wc_download_log` because it could not be opened.
2025-06-10T12:22:23.200633Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.200957Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.201259Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.201719Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_wc_order_coupon_lookup.ibd' OS error: 103
2025-06-10T12:22:23.202273Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.202621Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.203067Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_wc_order_coupon_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.203633Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_wc_order_coupon_lookup` because it could not be opened.
2025-06-10T12:22:23.204164Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.204422Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.204702Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.205154Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_wc_order_product_lookup.ibd' OS error: 103
2025-06-10T12:22:23.205517Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.205851Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.206271Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_wc_order_product_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.206913Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_wc_order_product_lookup` because it could not be opened.
2025-06-10T12:22:23.207329Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.207586Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.207956Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.208339Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_wc_order_stats.ibd' OS error: 103
2025-06-10T12:22:23.208672Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.209018Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.209418Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_wc_order_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.210075Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_wc_order_stats` because it could not be opened.
2025-06-10T12:22:23.210451Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.210713Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.211077Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.211492Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_wc_order_tax_lookup.ibd' OS error: 103
2025-06-10T12:22:23.212033Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.212319Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.212811Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_wc_order_tax_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.213507Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_wc_order_tax_lookup` because it could not be opened.
2025-06-10T12:22:23.214000Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.214257Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.214521Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.214947Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_wc_product_meta_lookup.ibd' OS error: 103
2025-06-10T12:22:23.215321Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.215604Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.216077Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_wc_product_meta_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.216678Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_wc_product_meta_lookup` because it could not be opened.
2025-06-10T12:22:23.217155Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.217413Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.217675Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.218136Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_wc_reserved_stock.ibd' OS error: 103
2025-06-10T12:22:23.218471Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.218769Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.219177Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_wc_reserved_stock`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.219797Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_wc_reserved_stock` because it could not be opened.
2025-06-10T12:22:23.220260Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.220540Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.220949Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.221356Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_wc_tax_rate_classes.ibd' OS error: 103
2025-06-10T12:22:23.221895Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.222195Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.222718Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_wc_tax_rate_classes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.223349Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_wc_tax_rate_classes` because it could not be opened.
2025-06-10T12:22:23.224139Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.225428Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.226132Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.226636Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_wc_webhooks.ibd' OS error: 103
2025-06-10T12:22:23.226980Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.227246Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.227716Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_wc_webhooks`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.228297Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_wc_webhooks` because it could not be opened.
2025-06-10T12:22:23.228764Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.229030Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.229501Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.229896Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_woocommerce_api_keys.ibd' OS error: 103
2025-06-10T12:22:23.230260Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.230638Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.231061Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_woocommerce_api_keys`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.231742Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_woocommerce_api_keys` because it could not be opened.
2025-06-10T12:22:23.232205Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.232556Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.232992Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.233520Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_woocommerce_attribute_taxonomies.ibd' OS error: 103
2025-06-10T12:22:23.234032Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.234340Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.234794Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_woocommerce_attribute_taxonomies`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.235385Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_woocommerce_attribute_taxonomies` because it could not be opened.
2025-06-10T12:22:23.235920Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.236176Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.236519Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.236904Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_woocommerce_downloadable_product_permissions.ibd' OS error: 103
2025-06-10T12:22:23.237295Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.237661Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.238072Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_woocommerce_downloadable_product_permissions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.238777Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_woocommerce_downloadable_product_permissions` because it could not be opened.
2025-06-10T12:22:23.239223Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.239553Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.239828Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.240197Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_woocommerce_log.ibd' OS error: 103
2025-06-10T12:22:23.240619Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.240871Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.241268Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_woocommerce_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.241924Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_woocommerce_log` because it could not be opened.
2025-06-10T12:22:23.242289Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.242623Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.243117Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.243607Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_woocommerce_order_itemmeta.ibd' OS error: 103
2025-06-10T12:22:23.244066Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.244476Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.244896Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_woocommerce_order_itemmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.245573Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_woocommerce_order_itemmeta` because it could not be opened.
2025-06-10T12:22:23.246009Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.246276Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.246626Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.247011Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_woocommerce_order_items.ibd' OS error: 103
2025-06-10T12:22:23.247416Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.247691Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.248105Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_woocommerce_order_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.248771Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_woocommerce_order_items` because it could not be opened.
2025-06-10T12:22:23.249466Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.249764Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.250050Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.250504Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_woocommerce_payment_tokenmeta.ibd' OS error: 103
2025-06-10T12:22:23.250884Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.251148Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.251632Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_woocommerce_payment_tokenmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.252257Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_woocommerce_payment_tokenmeta` because it could not be opened.
2025-06-10T12:22:23.252808Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.253073Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.253345Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.253816Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_woocommerce_payment_tokens.ibd' OS error: 103
2025-06-10T12:22:23.254341Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.254658Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.255072Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_woocommerce_payment_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.255750Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_woocommerce_payment_tokens` because it could not be opened.
2025-06-10T12:22:23.256153Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.256495Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.256750Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.257114Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_woocommerce_sessions.ibd' OS error: 103
2025-06-10T12:22:23.257546Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.257795Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.258190Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_woocommerce_sessions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.258832Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_woocommerce_sessions` because it could not be opened.
2025-06-10T12:22:23.259278Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.259639Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.259903Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.260265Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_woocommerce_shipping_zone_locations.ibd' OS error: 103
2025-06-10T12:22:23.260709Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.260957Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.261682Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_woocommerce_shipping_zone_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.263153Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_woocommerce_shipping_zone_locations` because it could not be opened.
2025-06-10T12:22:23.264314Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.264698Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.264976Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.265410Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_woocommerce_shipping_zone_methods.ibd' OS error: 103
2025-06-10T12:22:23.265794Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.266057Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.266521Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_woocommerce_shipping_zone_methods`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.267143Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_woocommerce_shipping_zone_methods` because it could not be opened.
2025-06-10T12:22:23.267641Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.267912Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.268215Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.268662Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_woocommerce_shipping_zones.ibd' OS error: 103
2025-06-10T12:22:23.269226Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.269550Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.269976Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_woocommerce_shipping_zones`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.270669Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_woocommerce_shipping_zones` because it could not be opened.
2025-06-10T12:22:23.271325Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.271611Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.271924Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.272361Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_woocommerce_tax_rate_locations.ibd' OS error: 103
2025-06-10T12:22:23.272764Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.273015Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.273485Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_woocommerce_tax_rate_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.274065Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_woocommerce_tax_rate_locations` because it could not be opened.
2025-06-10T12:22:23.274600Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.274848Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.275101Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.275628Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_woocommerce_tax_rates.ibd' OS error: 103
2025-06-10T12:22:23.276143Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.276551Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.276952Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_woocommerce_tax_rates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.277642Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_woocommerce_tax_rates` because it could not be opened.
2025-06-10T12:22:23.278044Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.278380Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.278661Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.279034Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_wpgmza.ibd' OS error: 103
2025-06-10T12:22:23.279408Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.279701Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.280128Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_wpgmza`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.280878Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_wpgmza` because it could not be opened.
2025-06-10T12:22:23.281309Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.281630Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.281907Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.282524Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_wpgmza_circles.ibd' OS error: 103
2025-06-10T12:22:23.282904Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.283183Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.283733Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_wpgmza_circles`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.284441Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_wpgmza_circles` because it could not be opened.
2025-06-10T12:22:23.284874Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.285132Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.285509Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.285878Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_wpgmza_maps.ibd' OS error: 103
2025-06-10T12:22:23.286190Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.286668Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.287096Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_wpgmza_maps`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.288248Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_wpgmza_maps` because it could not be opened.
2025-06-10T12:22:23.289594Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.289868Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.290486Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.290887Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_wpgmza_polygon.ibd' OS error: 103
2025-06-10T12:22:23.291281Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.291547Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.292039Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_wpgmza_polygon`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.292621Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_wpgmza_polygon` because it could not be opened.
2025-06-10T12:22:23.293113Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.293378Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.293647Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.294094Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_wpgmza_polylines.ibd' OS error: 103
2025-06-10T12:22:23.294447Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.294724Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.295294Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_wpgmza_polylines`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.295975Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_wpgmza_polylines` because it could not be opened.
2025-06-10T12:22:23.296426Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.296700Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.297070Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.297491Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_wpgmza_rectangles.ibd' OS error: 103
2025-06-10T12:22:23.297966Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.298359Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.298805Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_wpgmza_rectangles`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.299381Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_wpgmza_rectangles` because it could not be opened.
2025-06-10T12:22:23.299890Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.300167Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.300420Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.300862Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_wpie_template.ibd' OS error: 103
2025-06-10T12:22:23.301202Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.301446Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.301904Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_wpie_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.302443Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_wpie_template` because it could not be opened.
2025-06-10T12:22:23.302916Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.303176Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.303430Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.303880Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_wpmailsmtp_debug_events.ibd' OS error: 103
2025-06-10T12:22:23.304276Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.304527Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.304989Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_wpmailsmtp_debug_events`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.305558Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_wpmailsmtp_debug_events` because it could not be opened.
2025-06-10T12:22:23.306074Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.306326Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.306680Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.307111Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_wpmailsmtp_tasks_meta.ibd' OS error: 103
2025-06-10T12:22:23.307479Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.307813Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.308232Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_wpmailsmtp_tasks_meta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.308895Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_wpmailsmtp_tasks_meta` because it could not be opened.
2025-06-10T12:22:23.309318Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.309584Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.310092Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.310479Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:23.310883Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.311152Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.311547Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.312327Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:23.312817Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.313125Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.313386Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.313845Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:23.314265Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.314512Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.315031Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.315565Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:23.316031Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.316423Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.316722Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.317242Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:23.317559Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.317864Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.318271Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.318878Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:23.319296Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.319741Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.320081Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.320555Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem40\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:23.321073Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.321425Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.322084Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem40/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.322768Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem40/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:23.323367Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.323692Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.324016Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.324446Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:23.324847Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.325110Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.325510Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.326342Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:23.326852Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.327133Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.327409Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.327825Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_comments.ibd' OS error: 103
2025-06-10T12:22:23.328157Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.328442Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.328880Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.329539Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_comments` because it could not be opened.
2025-06-10T12:22:23.330038Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.330333Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.330595Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.331028Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:23.331331Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.331581Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.332101Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.332786Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_fbv` because it could not be opened.
2025-06-10T12:22:23.333189Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.333456Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.333759Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.334151Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:23.334508Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.334801Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.335222Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.336035Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:23.336764Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.337282Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.338092Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.338775Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_gg_attributes.ibd' OS error: 103
2025-06-10T12:22:23.339310Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.339589Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.339996Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_gg_attributes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.340660Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_gg_attributes` because it could not be opened.
2025-06-10T12:22:23.341078Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.341429Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.341691Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.342069Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_gg_cdn.ibd' OS error: 103
2025-06-10T12:22:23.342478Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.342968Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.343470Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_gg_cdn`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.344047Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_gg_cdn` because it could not be opened.
2025-06-10T12:22:23.344555Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.344834Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.345186Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.345703Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_gg_folders.ibd' OS error: 103
2025-06-10T12:22:23.346201Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.346471Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.346866Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_gg_folders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.347542Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_gg_folders` because it could not be opened.
2025-06-10T12:22:23.348014Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.348336Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.348622Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.349377Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_gg_galleries.ibd' OS error: 103
2025-06-10T12:22:23.349739Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.349991Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.350479Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_gg_galleries`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.351030Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_gg_galleries` because it could not be opened.
2025-06-10T12:22:23.351493Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.351837Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.352182Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.352579Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_gg_galleries_excluded.ibd' OS error: 103
2025-06-10T12:22:23.352915Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.353259Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.353672Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_gg_galleries_excluded`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.354319Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_gg_galleries_excluded` because it could not be opened.
2025-06-10T12:22:23.354814Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.355079Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.355440Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.355893Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_gg_galleries_resources.ibd' OS error: 103
2025-06-10T12:22:23.356312Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.356554Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.356942Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_gg_galleries_resources`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.357638Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_gg_galleries_resources` because it could not be opened.
2025-06-10T12:22:23.358024Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.358416Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.358687Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.359043Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_gg_image_optimize.ibd' OS error: 103
2025-06-10T12:22:23.359459Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.359706Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.360153Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_gg_image_optimize`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.360732Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_gg_image_optimize` because it could not be opened.
2025-06-10T12:22:23.361217Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.361484Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.361740Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.362234Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_gg_membership_presets.ibd' OS error: 103
2025-06-10T12:22:23.362621Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.362876Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.363331Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_gg_membership_presets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.363902Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_gg_membership_presets` because it could not be opened.
2025-06-10T12:22:23.364377Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.364637Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.365062Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.365513Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_gg_photos.ibd' OS error: 103
2025-06-10T12:22:23.365861Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.366213Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.366599Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_gg_photos`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.367221Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_gg_photos` because it could not be opened.
2025-06-10T12:22:23.367694Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.367943Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.368493Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.369208Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_gg_photos_pos.ibd' OS error: 103
2025-06-10T12:22:23.370403Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.370671Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.371154Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_gg_photos_pos`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.371793Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_gg_photos_pos` because it could not be opened.
2025-06-10T12:22:23.372324Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.372582Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.372887Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.373327Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_gg_photos_settings.ibd' OS error: 103
2025-06-10T12:22:23.373697Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.374046Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.374508Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_gg_photos_settings`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.375179Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_gg_photos_settings` because it could not be opened.
2025-06-10T12:22:23.375650Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.375998Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.376275Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.376881Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_gg_settings_presets.ibd' OS error: 103
2025-06-10T12:22:23.377268Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.377538Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.378061Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_gg_settings_presets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.378819Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_gg_settings_presets` because it could not be opened.
2025-06-10T12:22:23.379258Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.379524Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.379810Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.380222Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_gg_settings_sets.ibd' OS error: 103
2025-06-10T12:22:23.380567Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.380875Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.381295Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_gg_settings_sets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.381972Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_gg_settings_sets` because it could not be opened.
2025-06-10T12:22:23.382382Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.382648Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.382969Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.383392Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_gg_stats.ibd' OS error: 103
2025-06-10T12:22:23.383722Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.384006Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.384418Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_gg_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.385016Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_gg_stats` because it could not be opened.
2025-06-10T12:22:23.385552Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.385845Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.386119Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.386541Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_gg_tags.ibd' OS error: 103
2025-06-10T12:22:23.386914Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.387177Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.387584Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_gg_tags`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.388215Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_gg_tags` because it could not be opened.
2025-06-10T12:22:23.388583Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.388897Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.389178Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.389579Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_links.ibd' OS error: 103
2025-06-10T12:22:23.389942Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.390192Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.390586Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.391202Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_links` because it could not be opened.
2025-06-10T12:22:23.391554Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.391912Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.392249Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.392614Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_newsletter.ibd' OS error: 103
2025-06-10T12:22:23.393049Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.393311Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.393713Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_newsletter`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.394346Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_newsletter` because it could not be opened.
2025-06-10T12:22:23.394731Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.395111Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.395436Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.395900Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_newsletter_emails.ibd' OS error: 103
2025-06-10T12:22:23.396223Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.396471Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.397073Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_newsletter_emails`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.397936Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_newsletter_emails` because it could not be opened.
2025-06-10T12:22:23.398363Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.398613Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.398971Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.399345Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_newsletter_sent.ibd' OS error: 103
2025-06-10T12:22:23.399686Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.400215Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.400751Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_newsletter_sent`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.401356Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_newsletter_sent` because it could not be opened.
2025-06-10T12:22:23.402117Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.402394Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.402779Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.403164Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_newsletter_stats.ibd' OS error: 103
2025-06-10T12:22:23.403516Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.403918Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.404453Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_newsletter_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.405094Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_newsletter_stats` because it could not be opened.
2025-06-10T12:22:23.405554Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.405871Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.406154Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.406547Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_newsletter_user_logs.ibd' OS error: 103
2025-06-10T12:22:23.406943Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.407218Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.407644Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_newsletter_user_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.408292Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_newsletter_user_logs` because it could not be opened.
2025-06-10T12:22:23.408807Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.409092Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.409553Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.410046Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_options.ibd' OS error: 103
2025-06-10T12:22:23.410542Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.410862Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.411315Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.412061Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_options` because it could not be opened.
2025-06-10T12:22:23.412482Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.412821Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.413094Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.413458Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_post_views.ibd' OS error: 103
2025-06-10T12:22:23.413871Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.414126Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.414521Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_post_views`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.415186Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_post_views` because it could not be opened.
2025-06-10T12:22:23.415560Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.415875Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.416518Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.417007Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:23.417324Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.417574Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.418100Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.418758Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_postmeta` because it could not be opened.
2025-06-10T12:22:23.419251Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.419501Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.419887Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.420311Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_posts.ibd' OS error: 103
2025-06-10T12:22:23.420755Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.421032Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.421415Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.422075Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_posts` because it could not be opened.
2025-06-10T12:22:23.422706Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.423020Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.423282Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.423667Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_revslider_css.ibd' OS error: 103
2025-06-10T12:22:23.424158Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.424480Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.424967Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_revslider_css`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.425577Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_revslider_css` because it could not be opened.
2025-06-10T12:22:23.426168Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.426421Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.426808Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.427249Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_revslider_css_bkp.ibd' OS error: 103
2025-06-10T12:22:23.427571Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.427874Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.428291Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_revslider_css_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.428996Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_revslider_css_bkp` because it could not be opened.
2025-06-10T12:22:23.429655Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.429974Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.430233Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.430605Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_revslider_layer_animations.ibd' OS error: 103
2025-06-10T12:22:23.431026Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.431283Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.431753Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_revslider_layer_animations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.432414Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_revslider_layer_animations` because it could not be opened.
2025-06-10T12:22:23.432955Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.433385Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.433663Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.434508Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_revslider_layer_animations_bkp.ibd' OS error: 103
2025-06-10T12:22:23.435803Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.436299Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.436939Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_revslider_layer_animations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.437809Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_revslider_layer_animations_bkp` because it could not be opened.
2025-06-10T12:22:23.438423Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.438702Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.438992Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.439397Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_revslider_navigations.ibd' OS error: 103
2025-06-10T12:22:23.439754Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.440075Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.440506Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_revslider_navigations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.441322Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_revslider_navigations` because it could not be opened.
2025-06-10T12:22:23.442229Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.442657Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.443053Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.443509Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_revslider_navigations_bkp.ibd' OS error: 103
2025-06-10T12:22:23.443894Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.444223Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.444722Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_revslider_navigations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.445426Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_revslider_navigations_bkp` because it could not be opened.
2025-06-10T12:22:23.445849Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.446162Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.446425Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.446784Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_revslider_sliders.ibd' OS error: 103
2025-06-10T12:22:23.447221Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.447478Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.447865Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_revslider_sliders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.448573Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_revslider_sliders` because it could not be opened.
2025-06-10T12:22:23.448995Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.449310Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.449568Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.449924Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_revslider_sliders_bkp.ibd' OS error: 103
2025-06-10T12:22:23.450484Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.450803Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.451329Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_revslider_sliders_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.452208Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_revslider_sliders_bkp` because it could not be opened.
2025-06-10T12:22:23.452640Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.452897Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.453250Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.453615Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_revslider_slides.ibd' OS error: 103
2025-06-10T12:22:23.453950Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.454316Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.454769Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_revslider_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.455465Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_revslider_slides` because it could not be opened.
2025-06-10T12:22:23.455915Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.456222Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.456477Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.456836Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_revslider_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:23.457263Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.457513Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.457907Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_revslider_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.458792Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_revslider_slides_bkp` because it could not be opened.
2025-06-10T12:22:23.459537Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.459835Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.460177Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.460606Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_revslider_static_slides.ibd' OS error: 103
2025-06-10T12:22:23.460996Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.461272Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.461698Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_revslider_static_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.462358Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_revslider_static_slides` because it could not be opened.
2025-06-10T12:22:23.462937Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.463287Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.463573Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.464029Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_revslider_static_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:23.464435Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.465154Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.465679Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_revslider_static_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.466553Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_revslider_static_slides_bkp` because it could not be opened.
2025-06-10T12:22:23.467287Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.467590Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.467889Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.468299Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:23.468652Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.468914Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.469372Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.470004Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:23.470537Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.470792Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.471056Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.471499Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:23.471861Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.472117Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.472688Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.473307Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:23.473752Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.474177Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.474532Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.474980Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:23.475426Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.475732Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.476209Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.476845Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_termmeta` because it could not be opened.
2025-06-10T12:22:23.477304Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.477581Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.477889Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.478319Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_terms.ibd' OS error: 103
2025-06-10T12:22:23.478656Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.478926Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.479460Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.480026Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_terms` because it could not be opened.
2025-06-10T12:22:23.480502Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.480773Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.481045Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.481489Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:23.481819Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.482083Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.482612Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.483262Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_usermeta` because it could not be opened.
2025-06-10T12:22:23.483692Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.483973Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.484348Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.484761Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_users.ibd' OS error: 103
2025-06-10T12:22:23.485130Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.485499Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.485919Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.486557Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_users` because it could not be opened.
2025-06-10T12:22:23.486958Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.487350Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.487657Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.488021Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_wfblockediplog.ibd' OS error: 103
2025-06-10T12:22:23.488444Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.488733Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.489131Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_wfblockediplog`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.489814Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_wfblockediplog` because it could not be opened.
2025-06-10T12:22:23.490270Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.490587Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.490929Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.491457Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_wfblocks7.ibd' OS error: 103
2025-06-10T12:22:23.491770Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.492048Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.492543Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_wfblocks7`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.493174Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_wfblocks7` because it could not be opened.
2025-06-10T12:22:23.493607Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.493875Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.494145Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.494636Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_wfconfig.ibd' OS error: 103
2025-06-10T12:22:23.495095Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.495506Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.495911Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_wfconfig`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.496871Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_wfconfig` because it could not be opened.
2025-06-10T12:22:23.497299Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.497705Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.497984Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.498550Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_wfcrawlers.ibd' OS error: 103
2025-06-10T12:22:23.499152Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.499517Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.500062Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_wfcrawlers`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.500812Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_wfcrawlers` because it could not be opened.
2025-06-10T12:22:23.501257Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.501606Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.501879Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.502263Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_wffilechanges.ibd' OS error: 103
2025-06-10T12:22:23.502759Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.503072Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.503594Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_wffilechanges`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.504169Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_wffilechanges` because it could not be opened.
2025-06-10T12:22:23.504724Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.504988Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.505249Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.506058Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_wffilemods.ibd' OS error: 103
2025-06-10T12:22:23.506500Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.506756Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.507150Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_wffilemods`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.507934Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_wffilemods` because it could not be opened.
2025-06-10T12:22:23.508499Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.508773Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.509059Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.509555Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_wfhits.ibd' OS error: 103
2025-06-10T12:22:23.510053Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.510414Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.510829Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_wfhits`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.511441Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_wfhits` because it could not be opened.
2025-06-10T12:22:23.511825Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.512087Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.512419Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.512782Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_wfhoover.ibd' OS error: 103
2025-06-10T12:22:23.513166Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.513510Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.513945Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_wfhoover`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.514563Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_wfhoover` because it could not be opened.
2025-06-10T12:22:23.515027Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.515361Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.515632Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.516078Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_wfissues.ibd' OS error: 103
2025-06-10T12:22:23.516554Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.516815Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.517209Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_wfissues`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.518041Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_wfissues` because it could not be opened.
2025-06-10T12:22:23.518614Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.518978Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.519261Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.519746Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_wfknownfilelist.ibd' OS error: 103
2025-06-10T12:22:23.520080Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.520418Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.520842Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_wfknownfilelist`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.521527Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_wfknownfilelist` because it could not be opened.
2025-06-10T12:22:23.521905Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.522157Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.522487Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.523204Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_wflivetraffichuman.ibd' OS error: 103
2025-06-10T12:22:23.523621Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.523896Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.524356Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_wflivetraffichuman`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.524965Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_wflivetraffichuman` because it could not be opened.
2025-06-10T12:22:23.525546Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.525829Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.526108Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.526589Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_wflocs.ibd' OS error: 103
2025-06-10T12:22:23.526903Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.527260Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.527715Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_wflocs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.528334Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_wflocs` because it could not be opened.
2025-06-10T12:22:23.528885Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.529181Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.529586Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.530175Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_wflogins.ibd' OS error: 103
2025-06-10T12:22:23.530539Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.531219Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.531642Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_wflogins`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.532297Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_wflogins` because it could not be opened.
2025-06-10T12:22:23.532754Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.533024Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.533368Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.533754Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_wfls_2fa_secrets.ibd' OS error: 103
2025-06-10T12:22:23.534196Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.534466Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.534885Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_wfls_2fa_secrets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.535547Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_wfls_2fa_secrets` because it could not be opened.
2025-06-10T12:22:23.535994Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.536381Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.536664Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.537049Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_wfls_settings.ibd' OS error: 103
2025-06-10T12:22:23.537476Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.537755Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.538312Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_wfls_settings`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.539040Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_wfls_settings` because it could not be opened.
2025-06-10T12:22:23.539552Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.539804Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.540144Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.540566Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_wfnotifications.ibd' OS error: 103
2025-06-10T12:22:23.540895Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.541274Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.541670Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_wfnotifications`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.542477Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_wfnotifications` because it could not be opened.
2025-06-10T12:22:23.542905Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.543255Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.543519Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.543888Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_wfpendingissues.ibd' OS error: 103
2025-06-10T12:22:23.544307Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.544561Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.544956Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_wfpendingissues`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.545634Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_wfpendingissues` because it could not be opened.
2025-06-10T12:22:23.546017Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.546355Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.546611Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.546972Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_wfreversecache.ibd' OS error: 103
2025-06-10T12:22:23.547378Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.547628Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.548461Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_wfreversecache`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.549122Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_wfreversecache` because it could not be opened.
2025-06-10T12:22:23.549525Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.549780Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.550121Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.550539Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_wfsnipcache.ibd' OS error: 103
2025-06-10T12:22:23.550854Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.551185Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.551609Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_wfsnipcache`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.552281Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_wfsnipcache` because it could not be opened.
2025-06-10T12:22:23.552691Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.552939Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.553315Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.553670Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_wfstatus.ibd' OS error: 103
2025-06-10T12:22:23.553976Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.554368Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.554890Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_wfstatus`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.555474Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_wfstatus` because it could not be opened.
2025-06-10T12:22:23.555980Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.556391Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.556697Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.557199Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_wftrafficrates.ibd' OS error: 103
2025-06-10T12:22:23.557573Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.557823Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.558357Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_wftrafficrates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.558911Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_wftrafficrates` because it could not be opened.
2025-06-10T12:22:23.559383Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.559637Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.559894Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.560366Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_wpfm_backup.ibd' OS error: 103
2025-06-10T12:22:23.560848Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.561348Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.562491Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_wpfm_backup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.563330Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_wpfm_backup` because it could not be opened.
2025-06-10T12:22:23.563868Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.564223Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.564559Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.564975Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_yoast_seo_links.ibd' OS error: 103
2025-06-10T12:22:23.565349Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.565653Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.566084Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_yoast_seo_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.566742Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_yoast_seo_links` because it could not be opened.
2025-06-10T12:22:23.567140Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.567417Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.567910Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.568336Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem5\wp_yoast_seo_meta.ibd' OS error: 103
2025-06-10T12:22:23.568795Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.569051Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.569500Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem5/wp_yoast_seo_meta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.570101Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem5/wp_yoast_seo_meta` because it could not be opened.
2025-06-10T12:22:23.570683Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.570991Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.571368Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.571797Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsem50\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:23.572106Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.572355Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.572824Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsem50/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.573373Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsem50/wp_postmeta` because it could not be opened.
2025-06-10T12:22:23.573915Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.574172Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.574502Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.574878Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsemhbg\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:23.575201Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.575618Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.576074Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsemhbg/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.576728Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsemhbg/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:23.577164Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.577510Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.577791Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.578156Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsemhbg\wp_comments.ibd' OS error: 103
2025-06-10T12:22:23.578537Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.578787Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.579185Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsemhbg/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.579880Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsemhbg/wp_comments` because it could not be opened.
2025-06-10T12:22:23.580264Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.580578Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.580839Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.581209Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsemhbg\wp_links.ibd' OS error: 103
2025-06-10T12:22:23.581895Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.582173Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.582621Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsemhbg/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.583294Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsemhbg/wp_links` because it could not be opened.
2025-06-10T12:22:23.583752Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.584009Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.584269Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.584733Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsemhbg\wp_options.ibd' OS error: 103
2025-06-10T12:22:23.585093Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.585345Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.585863Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsemhbg/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.586532Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsemhbg/wp_options` because it could not be opened.
2025-06-10T12:22:23.587010Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.587263Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.587632Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.588059Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsemhbg\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:23.588421Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.588689Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.589087Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsemhbg/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.589697Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsemhbg/wp_postmeta` because it could not be opened.
2025-06-10T12:22:23.590211Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.590564Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.590957Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.591420Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsemhbg\wp_posts.ibd' OS error: 103
2025-06-10T12:22:23.591853Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.592098Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.592651Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsemhbg/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.593251Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsemhbg/wp_posts` because it could not be opened.
2025-06-10T12:22:23.593714Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.594076Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.594383Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.594831Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsemhbg\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:23.595256Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.595668Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.596079Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsemhbg/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.596715Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsemhbg/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:23.597138Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.597472Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.597751Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.598118Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsemhbg\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:23.598494Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.598756Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.599174Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsemhbg/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.599792Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsemhbg/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:23.600419Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.600736Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.601000Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.601615Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsemhbg\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:23.602033Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.602414Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.602909Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsemhbg/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.603547Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsemhbg/wp_termmeta` because it could not be opened.
2025-06-10T12:22:23.603944Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.604210Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.604665Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.605133Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsemhbg\wp_terms.ibd' OS error: 103
2025-06-10T12:22:23.605561Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.605814Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.606206Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsemhbg/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.606897Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsemhbg/wp_terms` because it could not be opened.
2025-06-10T12:22:23.607298Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.608409Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.608763Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.609692Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsemhbg\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:23.610224Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.610564Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.611024Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsemhbg/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.611665Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsemhbg/wp_usermeta` because it could not be opened.
2025-06-10T12:22:23.612151Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.612422Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.612781Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.613172Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsemhbg\wp_users.ibd' OS error: 103
2025-06-10T12:22:23.613516Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.613805Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.614417Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsemhbg/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.615118Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsemhbg/wp_users` because it could not be opened.
2025-06-10T12:22:23.615701Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.615993Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.616277Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.616783Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsemhbg\wp_wpfm_backup.ibd' OS error: 103
2025-06-10T12:22:23.617115Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.617375Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.617900Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsemhbg/wp_wpfm_backup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.618715Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsemhbg/wp_wpfm_backup` because it could not be opened.
2025-06-10T12:22:23.619147Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.619432Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.619836Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.620297Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsemhbg\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:23.620819Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.621193Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.621744Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsemhbg/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.622329Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsemhbg/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:23.622875Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.623144Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.623418Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.623874Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsemhbg\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:23.624213Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.624535Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.624955Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsemhbg/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.625604Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsemhbg/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:23.626003Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.626271Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.626604Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.626987Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsemhbg\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:23.627325Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.627730Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.628154Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsemhbg/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.628785Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsemhbg/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:23.629170Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.629466Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.629762Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.630240Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_carsemhbg\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:23.630676Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.630931Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.631326Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_carsemhbg/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.631967Z 0 [Warning] InnoDB: Ignoring tablespace `client_carsemhbg/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:23.632807Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.633077Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.633339Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.633846Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_ch666\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:23.634161Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.634427Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.634916Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_ch666/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.635617Z 0 [Warning] InnoDB: Ignoring tablespace `client_ch666/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:23.636024Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.636291Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.636771Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.637320Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_ch666\wp_comments.ibd' OS error: 103
2025-06-10T12:22:23.637883Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.638264Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.638957Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_ch666/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.639879Z 0 [Warning] InnoDB: Ignoring tablespace `client_ch666/wp_comments` because it could not be opened.
2025-06-10T12:22:23.640608Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.641511Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.642111Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.642619Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_ch666\wp_links.ibd' OS error: 103
2025-06-10T12:22:23.642983Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.643244Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.643708Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_ch666/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.644236Z 0 [Warning] InnoDB: Ignoring tablespace `client_ch666/wp_links` because it could not be opened.
2025-06-10T12:22:23.644701Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.644960Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.645222Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.645656Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_ch666\wp_options.ibd' OS error: 103
2025-06-10T12:22:23.645965Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.646220Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.646714Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_ch666/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.647272Z 0 [Warning] InnoDB: Ignoring tablespace `client_ch666/wp_options` because it could not be opened.
2025-06-10T12:22:23.647753Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.648014Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.648286Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.648911Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_ch666\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:23.649295Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.649709Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.650195Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_ch666/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.650952Z 0 [Warning] InnoDB: Ignoring tablespace `client_ch666/wp_postmeta` because it could not be opened.
2025-06-10T12:22:23.651429Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.651709Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.651983Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.652430Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_ch666\wp_posts.ibd' OS error: 103
2025-06-10T12:22:23.652749Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.653012Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.653498Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_ch666/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.654052Z 0 [Warning] InnoDB: Ignoring tablespace `client_ch666/wp_posts` because it could not be opened.
2025-06-10T12:22:23.654495Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.654758Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.655261Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.655856Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_ch666\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:23.656268Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.656773Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.657381Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_ch666/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.657997Z 0 [Warning] InnoDB: Ignoring tablespace `client_ch666/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:23.658511Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.658816Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.659080Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.659572Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_ch666\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:23.659901Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.660155Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.660614Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_ch666/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.661200Z 0 [Warning] InnoDB: Ignoring tablespace `client_ch666/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:23.661634Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.661903Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.662303Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.662700Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_ch666\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:23.663124Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.663503Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.663906Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_ch666/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.664524Z 0 [Warning] InnoDB: Ignoring tablespace `client_ch666/wp_termmeta` because it could not be opened.
2025-06-10T12:22:23.664900Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.665175Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.665563Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.665982Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_ch666\wp_terms.ibd' OS error: 103
2025-06-10T12:22:23.666316Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.666616Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.667015Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_ch666/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.667707Z 0 [Warning] InnoDB: Ignoring tablespace `client_ch666/wp_terms` because it could not be opened.
2025-06-10T12:22:23.668137Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.668859Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.669164Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.669585Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_ch666\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:23.669963Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.670289Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.670710Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_ch666/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.671300Z 0 [Warning] InnoDB: Ignoring tablespace `client_ch666/wp_usermeta` because it could not be opened.
2025-06-10T12:22:23.672198Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.673326Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.674378Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.674833Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_ch666\wp_users.ibd' OS error: 103
2025-06-10T12:22:23.675185Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.675451Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.675896Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_ch666/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.676457Z 0 [Warning] InnoDB: Ignoring tablespace `client_ch666/wp_users` because it could not be opened.
2025-06-10T12:22:23.677264Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.677538Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.677803Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.678296Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto1\wp_actionscheduler_actions.ibd' OS error: 103
2025-06-10T12:22:23.678646Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.678946Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.679443Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto1/wp_actionscheduler_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.680209Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto1/wp_actionscheduler_actions` because it could not be opened.
2025-06-10T12:22:23.680739Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.681149Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.681510Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.681976Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto1\wp_actionscheduler_claims.ibd' OS error: 103
2025-06-10T12:22:23.682517Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.682785Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.683252Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto1/wp_actionscheduler_claims`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.683827Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto1/wp_actionscheduler_claims` because it could not be opened.
2025-06-10T12:22:23.684323Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.684580Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.684838Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.685269Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto1\wp_actionscheduler_groups.ibd' OS error: 103
2025-06-10T12:22:23.685606Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.685869Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.686319Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto1/wp_actionscheduler_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.686945Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto1/wp_actionscheduler_groups` because it could not be opened.
2025-06-10T12:22:23.687368Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.687623Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.687914Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.688345Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto1\wp_actionscheduler_logs.ibd' OS error: 103
2025-06-10T12:22:23.688683Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.688980Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.689448Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto1/wp_actionscheduler_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.690127Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto1/wp_actionscheduler_logs` because it could not be opened.
2025-06-10T12:22:23.690553Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.690892Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.691168Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.691530Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto1\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:23.691854Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.692149Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.692560Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto1/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.693163Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto1/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:23.693541Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.693805Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.694103Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.694486Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto1\wp_comments.ibd' OS error: 103
2025-06-10T12:22:23.694813Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.695105Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.695522Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto1/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.696147Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto1/wp_comments` because it could not be opened.
2025-06-10T12:22:23.696517Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.696771Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.697130Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.697546Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto1\wp_links.ibd' OS error: 103
2025-06-10T12:22:23.697905Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.698179Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.698588Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto1/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.699180Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto1/wp_links` because it could not be opened.
2025-06-10T12:22:23.699566Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.699844Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.700144Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.700539Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto1\wp_options.ibd' OS error: 103
2025-06-10T12:22:23.701320Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.701649Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.702241Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto1/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.702787Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto1/wp_options` because it could not be opened.
2025-06-10T12:22:23.703291Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.703543Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.703799Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.704579Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto1\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:23.705443Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.706275Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.707206Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto1/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.707875Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto1/wp_postmeta` because it could not be opened.
2025-06-10T12:22:23.708308Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.708592Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.708886Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.709270Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto1\wp_posts.ibd' OS error: 103
2025-06-10T12:22:23.709591Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.709899Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.710488Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto1/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.711200Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto1/wp_posts` because it could not be opened.
2025-06-10T12:22:23.711696Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.712012Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.712294Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.712669Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto1\wp_sgpb_subscribers.ibd' OS error: 103
2025-06-10T12:22:23.713115Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.713371Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.713780Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto1/wp_sgpb_subscribers`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.714547Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto1/wp_sgpb_subscribers` because it could not be opened.
2025-06-10T12:22:23.715038Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.715296Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.715555Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.716195Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto1\wp_sgpb_subscription_error_log.ibd' OS error: 103
2025-06-10T12:22:23.716562Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.717061Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.717965Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto1/wp_sgpb_subscription_error_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.719269Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto1/wp_sgpb_subscription_error_log` because it could not be opened.
2025-06-10T12:22:23.720193Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.720617Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.721104Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.721732Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto1\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:23.722370Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.722808Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.723651Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto1/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.724640Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto1/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:23.725362Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.725817Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.726267Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.726927Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto1\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:23.727493Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.727956Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.728634Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto1/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.729352Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto1/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:23.729821Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.730104Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.730382Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.730857Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto1\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:23.731261Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.731522Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.731997Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto1/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.732562Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto1/wp_termmeta` because it could not be opened.
2025-06-10T12:22:23.733332Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.733748Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.734061Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.734433Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto1\wp_terms.ibd' OS error: 103
2025-06-10T12:22:23.734831Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.735095Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.735486Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto1/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.737024Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto1/wp_terms` because it could not be opened.
2025-06-10T12:22:23.738465Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.738741Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.739174Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.739566Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto1\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:23.739929Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.740192Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.740612Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto1/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.741216Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto1/wp_usermeta` because it could not be opened.
2025-06-10T12:22:23.741645Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.741978Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.742257Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.742650Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto1\wp_users.ibd' OS error: 103
2025-06-10T12:22:23.743010Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.743281Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.743704Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto1/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.744351Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto1/wp_users` because it could not be opened.
2025-06-10T12:22:23.744911Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.745194Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.745476Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.745994Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto1\wp_wc_admin_note_actions.ibd' OS error: 103
2025-06-10T12:22:23.746425Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.746715Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.747210Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto1/wp_wc_admin_note_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.747963Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto1/wp_wc_admin_note_actions` because it could not be opened.
2025-06-10T12:22:23.748477Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.748773Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.749056Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.749449Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto1\wp_wc_admin_notes.ibd' OS error: 103
2025-06-10T12:22:23.749840Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.750122Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.750742Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto1/wp_wc_admin_notes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.751375Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto1/wp_wc_admin_notes` because it could not be opened.
2025-06-10T12:22:23.751834Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.752113Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.752387Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.752807Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto1\wp_wc_category_lookup.ibd' OS error: 103
2025-06-10T12:22:23.753161Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.753424Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.753877Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto1/wp_wc_category_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.754459Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto1/wp_wc_category_lookup` because it could not be opened.
2025-06-10T12:22:23.754897Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.755163Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.755435Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.755866Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto1\wp_wc_customer_lookup.ibd' OS error: 103
2025-06-10T12:22:23.756212Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.756472Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.757008Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto1/wp_wc_customer_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.757618Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto1/wp_wc_customer_lookup` because it could not be opened.
2025-06-10T12:22:23.758048Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.758311Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.758583Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.758992Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto1\wp_wc_download_log.ibd' OS error: 103
2025-06-10T12:22:23.759333Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.759594Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.760031Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto1/wp_wc_download_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.760609Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto1/wp_wc_download_log` because it could not be opened.
2025-06-10T12:22:23.761047Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.761311Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.761580Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.762032Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto1\wp_wc_order_coupon_lookup.ibd' OS error: 103
2025-06-10T12:22:23.762394Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.762751Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.763451Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto1/wp_wc_order_coupon_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.764167Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto1/wp_wc_order_coupon_lookup` because it could not be opened.
2025-06-10T12:22:23.764846Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.765204Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.765503Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.766008Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto1\wp_wc_order_product_lookup.ibd' OS error: 103
2025-06-10T12:22:23.766350Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.766598Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.767103Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto1/wp_wc_order_product_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.767663Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto1/wp_wc_order_product_lookup` because it could not be opened.
2025-06-10T12:22:23.768244Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.768697Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.769229Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.770294Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto1\wp_wc_order_stats.ibd' OS error: 103
2025-06-10T12:22:23.770762Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.771187Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.771834Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto1/wp_wc_order_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.772543Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto1/wp_wc_order_stats` because it could not be opened.
2025-06-10T12:22:23.772987Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.773277Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.773570Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.773957Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto1\wp_wc_order_tax_lookup.ibd' OS error: 103
2025-06-10T12:22:23.774307Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.774603Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.775016Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto1/wp_wc_order_tax_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.775703Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto1/wp_wc_order_tax_lookup` because it could not be opened.
2025-06-10T12:22:23.776148Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.776450Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.776874Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.777264Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto1\wp_wc_product_meta_lookup.ibd' OS error: 103
2025-06-10T12:22:23.777651Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.777921Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.778359Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto1/wp_wc_product_meta_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.779146Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto1/wp_wc_product_meta_lookup` because it could not be opened.
2025-06-10T12:22:23.779687Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.779973Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.780247Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.780727Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto1\wp_wc_reserved_stock.ibd' OS error: 103
2025-06-10T12:22:23.781056Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.781310Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.781797Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto1/wp_wc_reserved_stock`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.782350Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto1/wp_wc_reserved_stock` because it could not be opened.
2025-06-10T12:22:23.782813Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.783065Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.783325Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.783780Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto1\wp_wc_tax_rate_classes.ibd' OS error: 103
2025-06-10T12:22:23.784111Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.784358Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.784806Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto1/wp_wc_tax_rate_classes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.785353Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto1/wp_wc_tax_rate_classes` because it could not be opened.
2025-06-10T12:22:23.785815Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.786061Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.786313Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.786836Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto1\wp_wc_webhooks.ibd' OS error: 103
2025-06-10T12:22:23.787143Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.787418Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.788058Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto1/wp_wc_webhooks`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.788739Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto1/wp_wc_webhooks` because it could not be opened.
2025-06-10T12:22:23.789203Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.789529Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.789805Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.790191Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto1\wp_woocommerce_api_keys.ibd' OS error: 103
2025-06-10T12:22:23.790667Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.791128Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.791662Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto1/wp_woocommerce_api_keys`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.792211Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto1/wp_woocommerce_api_keys` because it could not be opened.
2025-06-10T12:22:23.792883Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.793206Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.793620Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.794004Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto1\wp_woocommerce_attribute_taxonomies.ibd' OS error: 103
2025-06-10T12:22:23.794438Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.794759Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.795184Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto1/wp_woocommerce_attribute_taxonomies`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.795917Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto1/wp_woocommerce_attribute_taxonomies` because it could not be opened.
2025-06-10T12:22:23.796469Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.796806Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.797100Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.797634Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto1\wp_woocommerce_downloadable_product_permissions.ibd' OS error: 103
2025-06-10T12:22:23.798108Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.798617Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.799055Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto1/wp_woocommerce_downloadable_product_permissions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.800256Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto1/wp_woocommerce_downloadable_product_permissions` because it could not be opened.
2025-06-10T12:22:23.801194Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.801618Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.802411Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.802956Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto1\wp_woocommerce_log.ibd' OS error: 103
2025-06-10T12:22:23.803462Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.803735Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.804172Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto1/wp_woocommerce_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.804766Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto1/wp_woocommerce_log` because it could not be opened.
2025-06-10T12:22:23.805225Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.805511Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.805785Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.806171Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto1\wp_woocommerce_order_itemmeta.ibd' OS error: 103
2025-06-10T12:22:23.806788Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.807101Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.807652Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto1/wp_woocommerce_order_itemmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.808259Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto1/wp_woocommerce_order_itemmeta` because it could not be opened.
2025-06-10T12:22:23.808855Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.809122Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.809503Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.810177Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto1\wp_woocommerce_order_items.ibd' OS error: 103
2025-06-10T12:22:23.810606Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.810898Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.811309Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto1/wp_woocommerce_order_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.811959Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto1/wp_woocommerce_order_items` because it could not be opened.
2025-06-10T12:22:23.812444Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.812719Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.812982Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.813641Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto1\wp_woocommerce_payment_tokenmeta.ibd' OS error: 103
2025-06-10T12:22:23.814054Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.814320Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.814781Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto1/wp_woocommerce_payment_tokenmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.815433Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto1/wp_woocommerce_payment_tokenmeta` because it could not be opened.
2025-06-10T12:22:23.815943Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.816200Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.816569Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.816979Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto1\wp_woocommerce_payment_tokens.ibd' OS error: 103
2025-06-10T12:22:23.817413Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.817688Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.818087Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto1/wp_woocommerce_payment_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.818724Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto1/wp_woocommerce_payment_tokens` because it could not be opened.
2025-06-10T12:22:23.819136Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.819471Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.819958Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.820409Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto1\wp_woocommerce_sessions.ibd' OS error: 103
2025-06-10T12:22:23.820766Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.821061Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.821597Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto1/wp_woocommerce_sessions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.822158Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto1/wp_woocommerce_sessions` because it could not be opened.
2025-06-10T12:22:23.822690Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.822945Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.823206Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.823697Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto1\wp_woocommerce_shipping_zone_locations.ibd' OS error: 103
2025-06-10T12:22:23.824064Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.824434Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.824968Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto1/wp_woocommerce_shipping_zone_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.825639Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto1/wp_woocommerce_shipping_zone_locations` because it could not be opened.
2025-06-10T12:22:23.826152Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.826589Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.826911Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.827328Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto1\wp_woocommerce_shipping_zone_methods.ibd' OS error: 103
2025-06-10T12:22:23.827748Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.828005Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.828479Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto1/wp_woocommerce_shipping_zone_methods`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.829093Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto1/wp_woocommerce_shipping_zone_methods` because it could not be opened.
2025-06-10T12:22:23.829658Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.829915Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.830177Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.830611Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto1\wp_woocommerce_shipping_zones.ibd' OS error: 103
2025-06-10T12:22:23.830966Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.831250Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.831748Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto1/wp_woocommerce_shipping_zones`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.832625Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto1/wp_woocommerce_shipping_zones` because it could not be opened.
2025-06-10T12:22:23.833960Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.834820Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.835198Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.835589Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto1\wp_woocommerce_tax_rate_locations.ibd' OS error: 103
2025-06-10T12:22:23.835967Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.836274Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.836690Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto1/wp_woocommerce_tax_rate_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.837347Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto1/wp_woocommerce_tax_rate_locations` because it could not be opened.
2025-06-10T12:22:23.837822Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.838146Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.838410Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.838796Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto1\wp_woocommerce_tax_rates.ibd' OS error: 103
2025-06-10T12:22:23.839197Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.839461Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.839966Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto1/wp_woocommerce_tax_rates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.840629Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto1/wp_woocommerce_tax_rates` because it could not be opened.
2025-06-10T12:22:23.841130Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.841417Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.841711Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.842283Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto1\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:23.842658Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.843036Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.843489Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto1/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.844234Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto1/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:23.844673Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.844937Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.845250Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.845635Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto1\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:23.845977Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.846293Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.846704Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto1/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.847313Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto1/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:23.847700Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.847986Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.848272Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.848650Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto1\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:23.849020Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.849288Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.849702Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto1/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.850315Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto1/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:23.850683Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.850960Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.851260Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.851650Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto1\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:23.852078Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.852376Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.852769Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto1/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.853408Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto1/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:23.853790Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.854103Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.854703Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.855147Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto2\wp_actionscheduler_actions.ibd' OS error: 103
2025-06-10T12:22:23.855493Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.855748Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.856252Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto2/wp_actionscheduler_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.856853Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto2/wp_actionscheduler_actions` because it could not be opened.
2025-06-10T12:22:23.857358Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.857612Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.857872Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.858356Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto2\wp_actionscheduler_claims.ibd' OS error: 103
2025-06-10T12:22:23.858725Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.859061Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.859476Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto2/wp_actionscheduler_claims`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.860103Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto2/wp_actionscheduler_claims` because it could not be opened.
2025-06-10T12:22:23.860499Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.860752Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.861072Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.861437Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto2\wp_actionscheduler_groups.ibd' OS error: 103
2025-06-10T12:22:23.861779Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.862090Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.862492Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto2/wp_actionscheduler_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.863116Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto2/wp_actionscheduler_groups` because it could not be opened.
2025-06-10T12:22:23.863583Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.863857Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.864217Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.864585Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto2\wp_actionscheduler_logs.ibd' OS error: 103
2025-06-10T12:22:23.865038Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.865321Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.865713Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto2/wp_actionscheduler_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.866338Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto2/wp_actionscheduler_logs` because it could not be opened.
2025-06-10T12:22:23.866726Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.867040Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.867331Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.867694Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto2\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:23.868071Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.868322Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.868711Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto2/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.869339Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto2/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:23.869698Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.870029Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.870304Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.870666Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto2\wp_comments.ibd' OS error: 103
2025-06-10T12:22:23.871118Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.871382Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.871774Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto2/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.872497Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto2/wp_comments` because it could not be opened.
2025-06-10T12:22:23.872857Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.873221Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.873580Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.874165Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto2\wp_links.ibd' OS error: 103
2025-06-10T12:22:23.874475Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.874725Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.875216Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto2/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.875749Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto2/wp_links` because it could not be opened.
2025-06-10T12:22:23.876276Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.876581Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.876855Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.877351Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto2\wp_options.ibd' OS error: 103
2025-06-10T12:22:23.877662Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.877941Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.878402Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto2/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.878999Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto2/wp_options` because it could not be opened.
2025-06-10T12:22:23.879390Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.879636Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.880038Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.880904Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto2\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:23.881237Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.881638Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.882098Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto2/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.883167Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto2/wp_postmeta` because it could not be opened.
2025-06-10T12:22:23.883713Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.884042Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.884375Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.884749Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto2\wp_posts.ibd' OS error: 103
2025-06-10T12:22:23.885056Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.885429Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.885833Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto2/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.886529Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto2/wp_posts` because it could not be opened.
2025-06-10T12:22:23.886948Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.887335Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.887599Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.887971Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto2\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:23.888414Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.888720Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.889328Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto2/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.889990Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto2/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:23.890545Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.890868Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.891209Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.891576Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto2\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:23.891897Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.892207Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.892666Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto2/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.893254Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto2/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:23.893637Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.893888Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.894230Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.894762Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto2\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:23.895120Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.895404Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.895800Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto2/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.896642Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto2/wp_termmeta` because it could not be opened.
2025-06-10T12:22:23.897257Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.897600Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.897909Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.898317Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto2\wp_terms.ibd' OS error: 103
2025-06-10T12:22:23.898658Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.898907Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.899475Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto2/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.900005Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto2/wp_terms` because it could not be opened.
2025-06-10T12:22:23.900465Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.900751Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.901073Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.901465Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto2\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:23.901790Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.902112Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.902526Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto2/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.903137Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto2/wp_usermeta` because it could not be opened.
2025-06-10T12:22:23.903511Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.903778Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.904207Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.904638Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto2\wp_users.ibd' OS error: 103
2025-06-10T12:22:23.904945Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.905347Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.905743Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto2/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.906425Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto2/wp_users` because it could not be opened.
2025-06-10T12:22:23.906804Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.907180Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.907441Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.907806Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto2\wp_wc_admin_note_actions.ibd' OS error: 103
2025-06-10T12:22:23.908263Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.908513Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.908969Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto2/wp_wc_admin_note_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.909706Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto2/wp_wc_admin_note_actions` because it could not be opened.
2025-06-10T12:22:23.910298Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.910576Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.910846Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.911279Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto2\wp_wc_admin_notes.ibd' OS error: 103
2025-06-10T12:22:23.911603Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.911855Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.912592Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto2/wp_wc_admin_notes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.914064Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto2/wp_wc_admin_notes` because it could not be opened.
2025-06-10T12:22:23.915299Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.915586Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.915936Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.916379Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto2\wp_wc_category_lookup.ibd' OS error: 103
2025-06-10T12:22:23.916732Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.916997Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.917490Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto2/wp_wc_category_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.918081Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto2/wp_wc_category_lookup` because it could not be opened.
2025-06-10T12:22:23.918575Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.918846Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.919325Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.919781Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto2\wp_wc_customer_lookup.ibd' OS error: 103
2025-06-10T12:22:23.920140Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.920452Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.920898Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto2/wp_wc_customer_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.921597Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto2/wp_wc_customer_lookup` because it could not be opened.
2025-06-10T12:22:23.922093Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.922652Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.922941Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.923373Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto2\wp_wc_download_log.ibd' OS error: 103
2025-06-10T12:22:23.923712Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.924022Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.924554Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto2/wp_wc_download_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.925111Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto2/wp_wc_download_log` because it could not be opened.
2025-06-10T12:22:23.925606Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.925865Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.926122Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.926690Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto2\wp_wc_order_coupon_lookup.ibd' OS error: 103
2025-06-10T12:22:23.927043Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.927416Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.927814Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto2/wp_wc_order_coupon_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.928461Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto2/wp_wc_order_coupon_lookup` because it could not be opened.
2025-06-10T12:22:23.928870Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.929126Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.929472Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.929835Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto2\wp_wc_order_product_lookup.ibd' OS error: 103
2025-06-10T12:22:23.930310Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.930578Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.930970Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto2/wp_wc_order_product_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.931592Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto2/wp_wc_order_product_lookup` because it could not be opened.
2025-06-10T12:22:23.931989Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.932346Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.932607Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.932968Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto2\wp_wc_order_stats.ibd' OS error: 103
2025-06-10T12:22:23.933356Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.933607Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.934002Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto2/wp_wc_order_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.934641Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto2/wp_wc_order_stats` because it could not be opened.
2025-06-10T12:22:23.935022Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.935353Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.935678Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.936046Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto2\wp_wc_order_tax_lookup.ibd' OS error: 103
2025-06-10T12:22:23.936675Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.937018Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.937588Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto2/wp_wc_order_tax_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.938246Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto2/wp_wc_order_tax_lookup` because it could not be opened.
2025-06-10T12:22:23.938686Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.938958Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.939292Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.939678Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto2\wp_wc_product_meta_lookup.ibd' OS error: 103
2025-06-10T12:22:23.940034Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.940372Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.940771Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto2/wp_wc_product_meta_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.941660Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto2/wp_wc_product_meta_lookup` because it could not be opened.
2025-06-10T12:22:23.942251Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.942569Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.942824Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.943263Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto2\wp_wc_reserved_stock.ibd' OS error: 103
2025-06-10T12:22:23.943639Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.943897Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.944538Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto2/wp_wc_reserved_stock`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.945247Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto2/wp_wc_reserved_stock` because it could not be opened.
2025-06-10T12:22:23.945854Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.946270Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.946549Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.947055Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto2\wp_wc_tax_rate_classes.ibd' OS error: 103
2025-06-10T12:22:23.947481Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.947891Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.948339Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto2/wp_wc_tax_rate_classes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.948958Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto2/wp_wc_tax_rate_classes` because it could not be opened.
2025-06-10T12:22:23.949415Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.949688Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.950002Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.950399Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto2\wp_wc_webhooks.ibd' OS error: 103
2025-06-10T12:22:23.950726Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.951093Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.951784Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto2/wp_wc_webhooks`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.952685Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto2/wp_wc_webhooks` because it could not be opened.
2025-06-10T12:22:23.953436Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.953823Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.954333Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.954944Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto2\wp_woocommerce_api_keys.ibd' OS error: 103
2025-06-10T12:22:23.955474Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.955942Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.956553Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto2/wp_woocommerce_api_keys`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.957464Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto2/wp_woocommerce_api_keys` because it could not be opened.
2025-06-10T12:22:23.958131Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.958508Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.958974Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.959502Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto2\wp_woocommerce_attribute_taxonomies.ibd' OS error: 103
2025-06-10T12:22:23.959962Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.960268Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.960666Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto2/wp_woocommerce_attribute_taxonomies`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.961311Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto2/wp_woocommerce_attribute_taxonomies` because it could not be opened.
2025-06-10T12:22:23.961739Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.962064Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.962321Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.962687Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto2\wp_woocommerce_downloadable_product_permissions.ibd' OS error: 103
2025-06-10T12:22:23.963166Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.963419Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.963889Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto2/wp_woocommerce_downloadable_product_permissions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.964549Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto2/wp_woocommerce_downloadable_product_permissions` because it could not be opened.
2025-06-10T12:22:23.965034Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.965377Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.965653Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.966100Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto2\wp_woocommerce_log.ibd' OS error: 103
2025-06-10T12:22:23.966477Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.966789Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.967528Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto2/wp_woocommerce_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.968144Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto2/wp_woocommerce_log` because it could not be opened.
2025-06-10T12:22:23.968569Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.968955Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.969229Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.969613Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto2\wp_woocommerce_order_itemmeta.ibd' OS error: 103
2025-06-10T12:22:23.970129Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.970513Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.971060Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto2/wp_woocommerce_order_itemmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.971645Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto2/wp_woocommerce_order_itemmeta` because it could not be opened.
2025-06-10T12:22:23.972229Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.972489Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.972752Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.973217Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto2\wp_woocommerce_order_items.ibd' OS error: 103
2025-06-10T12:22:23.973566Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.973896Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.974345Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto2/wp_woocommerce_order_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.975025Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto2/wp_woocommerce_order_items` because it could not be opened.
2025-06-10T12:22:23.975486Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.975780Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.976086Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.976952Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto2\wp_woocommerce_payment_tokenmeta.ibd' OS error: 103
2025-06-10T12:22:23.977325Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.978046Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.978457Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto2/wp_woocommerce_payment_tokenmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.979270Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto2/wp_woocommerce_payment_tokenmeta` because it could not be opened.
2025-06-10T12:22:23.979876Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.980150Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.980571Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.981030Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto2\wp_woocommerce_payment_tokens.ibd' OS error: 103
2025-06-10T12:22:23.981454Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.981724Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.982656Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto2/wp_woocommerce_payment_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.983425Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto2/wp_woocommerce_payment_tokens` because it could not be opened.
2025-06-10T12:22:23.983925Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.984481Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.984876Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.985564Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto2\wp_woocommerce_sessions.ibd' OS error: 103
2025-06-10T12:22:23.986064Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.986623Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.987085Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto2/wp_woocommerce_sessions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.988159Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto2/wp_woocommerce_sessions` because it could not be opened.
2025-06-10T12:22:23.988712Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.988980Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.989296Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.989677Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto2\wp_woocommerce_shipping_zone_locations.ibd' OS error: 103
2025-06-10T12:22:23.990044Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.990386Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.990795Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto2/wp_woocommerce_shipping_zone_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.991459Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto2/wp_woocommerce_shipping_zone_locations` because it could not be opened.
2025-06-10T12:22:23.991890Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.992195Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.992478Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.992850Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto2\wp_woocommerce_shipping_zone_methods.ibd' OS error: 103
2025-06-10T12:22:23.993325Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.993640Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.994072Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto2/wp_woocommerce_shipping_zone_methods`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.994770Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto2/wp_woocommerce_shipping_zone_methods` because it could not be opened.
2025-06-10T12:22:23.995328Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.995643Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.995906Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.996324Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto2\wp_woocommerce_shipping_zones.ibd' OS error: 103
2025-06-10T12:22:23.996675Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:23.996926Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:23.997443Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto2/wp_woocommerce_shipping_zones`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:23.998011Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto2/wp_woocommerce_shipping_zones` because it could not be opened.
2025-06-10T12:22:23.998517Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:23.998770Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:23.999040Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:23.999531Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto2\wp_woocommerce_tax_rate_locations.ibd' OS error: 103
2025-06-10T12:22:23.999891Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.000239Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.000662Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto2/wp_woocommerce_tax_rate_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.001350Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto2/wp_woocommerce_tax_rate_locations` because it could not be opened.
2025-06-10T12:22:24.001811Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.002063Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.002451Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.002873Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto2\wp_woocommerce_tax_rates.ibd' OS error: 103
2025-06-10T12:22:24.003434Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.003838Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.004521Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto2/wp_woocommerce_tax_rates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.005197Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto2/wp_woocommerce_tax_rates` because it could not be opened.
2025-06-10T12:22:24.005670Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.005953Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.006552Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.007125Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto2\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:24.007641Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.007926Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.008491Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto2/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.009242Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto2/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:24.010491Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.010765Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.011103Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.011497Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto2\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:24.011968Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.012272Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.012707Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto2/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.013301Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto2/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:24.014092Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.014369Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.014630Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.015105Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto2\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:24.015426Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.015699Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.016203Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto2/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.016871Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto2/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:24.017854Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.018542Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.018983Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.019424Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_clauto2\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:24.019841Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.020100Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.020501Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_clauto2/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.021140Z 0 [Warning] InnoDB: Ignoring tablespace `client_clauto2/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:24.021902Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.022190Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.022462Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.022898Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_actionscheduler_actions.ibd' OS error: 103
2025-06-10T12:22:24.023253Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.023506Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.023987Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_actionscheduler_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.024626Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_actionscheduler_actions` because it could not be opened.
2025-06-10T12:22:24.025164Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.025421Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.025677Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.026243Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_actionscheduler_claims.ibd' OS error: 103
2025-06-10T12:22:24.026586Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.026911Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.027468Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_actionscheduler_claims`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.028211Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_actionscheduler_claims` because it could not be opened.
2025-06-10T12:22:24.028628Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.028998Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.029364Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.029773Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_actionscheduler_groups.ibd' OS error: 103
2025-06-10T12:22:24.030123Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.030382Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.030950Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_actionscheduler_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.031726Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_actionscheduler_groups` because it could not be opened.
2025-06-10T12:22:24.032189Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.032464Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.032934Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.033342Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_actionscheduler_logs.ibd' OS error: 103
2025-06-10T12:22:24.033733Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.034014Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.034416Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_actionscheduler_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.035039Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_actionscheduler_logs` because it could not be opened.
2025-06-10T12:22:24.035469Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.035799Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.036107Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.036628Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_chaty_contact_form_leads.ibd' OS error: 103
2025-06-10T12:22:24.037069Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.037551Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.038100Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_chaty_contact_form_leads`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.038733Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_chaty_contact_form_leads` because it could not be opened.
2025-06-10T12:22:24.039372Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.039673Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.040043Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.040574Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:24.041150Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.041420Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.042350Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.042942Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:24.043432Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.043770Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.044047Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.044437Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_comments.ibd' OS error: 103
2025-06-10T12:22:24.044869Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.045141Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.045557Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.046184Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_comments` because it could not be opened.
2025-06-10T12:22:24.046631Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.046993Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.047308Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.047739Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:24.048270Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.048634Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.049171Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.049830Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_fbv` because it could not be opened.
2025-06-10T12:22:24.050451Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.050813Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.051113Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.051479Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:24.051917Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.052287Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.052791Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.053440Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:24.054056Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.054454Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.054864Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.055266Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_itsec_bans.ibd' OS error: 103
2025-06-10T12:22:24.055607Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.056051Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.056545Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_itsec_bans`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.057221Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_itsec_bans` because it could not be opened.
2025-06-10T12:22:24.057713Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.058021Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.058294Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.058975Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_itsec_dashboard_events.ibd' OS error: 103
2025-06-10T12:22:24.059385Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.059684Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.060141Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_itsec_dashboard_events`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.060768Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_itsec_dashboard_events` because it could not be opened.
2025-06-10T12:22:24.061292Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.061549Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.061871Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.062274Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_itsec_distributed_storage.ibd' OS error: 103
2025-06-10T12:22:24.062642Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.062932Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.063337Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_itsec_distributed_storage`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.064058Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_itsec_distributed_storage` because it could not be opened.
2025-06-10T12:22:24.064535Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.064840Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.065101Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.065470Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_itsec_fingerprints.ibd' OS error: 103
2025-06-10T12:22:24.065865Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.066140Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.066587Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_itsec_fingerprints`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.067261Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_itsec_fingerprints` because it could not be opened.
2025-06-10T12:22:24.067853Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.068137Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.068406Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.068920Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_itsec_geolocation_cache.ibd' OS error: 103
2025-06-10T12:22:24.069268Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.069523Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.070004Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_itsec_geolocation_cache`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.070574Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_itsec_geolocation_cache` because it could not be opened.
2025-06-10T12:22:24.071068Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.071343Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.071854Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.072498Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_itsec_lockouts.ibd' OS error: 103
2025-06-10T12:22:24.072923Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.073864Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.074532Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_itsec_lockouts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.075213Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_itsec_lockouts` because it could not be opened.
2025-06-10T12:22:24.075667Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.075955Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.076244Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.076661Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_itsec_logs.ibd' OS error: 103
2025-06-10T12:22:24.076998Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.077266Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.077715Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_itsec_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.078287Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_itsec_logs` because it could not be opened.
2025-06-10T12:22:24.078733Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.079001Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.079277Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.079770Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_itsec_mutexes.ibd' OS error: 103
2025-06-10T12:22:24.080131Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.080411Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.080903Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_itsec_mutexes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.081502Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_itsec_mutexes` because it could not be opened.
2025-06-10T12:22:24.082082Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.082371Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.082687Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.083098Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_itsec_opaque_tokens.ibd' OS error: 103
2025-06-10T12:22:24.083441Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.083790Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.084219Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_itsec_opaque_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.084968Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_itsec_opaque_tokens` because it could not be opened.
2025-06-10T12:22:24.085392Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.085691Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.085975Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.086476Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_itsec_temp.ibd' OS error: 103
2025-06-10T12:22:24.087032Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.087368Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.087861Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_itsec_temp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.088519Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_itsec_temp` because it could not be opened.
2025-06-10T12:22:24.089014Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.089261Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.089512Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.089981Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_itsec_user_groups.ibd' OS error: 103
2025-06-10T12:22:24.090310Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.090607Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.091038Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_itsec_user_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.091606Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_itsec_user_groups` because it could not be opened.
2025-06-10T12:22:24.092117Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.092469Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.093055Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.093502Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_kbp_countdown_entry.ibd' OS error: 103
2025-06-10T12:22:24.094153Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.094429Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.095040Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_kbp_countdown_entry`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.095720Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_kbp_countdown_entry` because it could not be opened.
2025-06-10T12:22:24.096180Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.096437Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.096778Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.097157Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_kbp_form_entry.ibd' OS error: 103
2025-06-10T12:22:24.097472Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.097761Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.098143Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_kbp_form_entry`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.098804Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_kbp_form_entry` because it could not be opened.
2025-06-10T12:22:24.099270Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.099547Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.099874Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.100236Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_kbp_form_entrymeta.ibd' OS error: 103
2025-06-10T12:22:24.100661Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.101062Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.101574Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_kbp_form_entrymeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.102207Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_kbp_form_entrymeta` because it could not be opened.
2025-06-10T12:22:24.102629Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.102894Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.103152Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.103556Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_links.ibd' OS error: 103
2025-06-10T12:22:24.103947Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.104243Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.104711Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.105286Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_links` because it could not be opened.
2025-06-10T12:22:24.105751Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.106063Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.106384Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.106796Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_litespeed_url.ibd' OS error: 103
2025-06-10T12:22:24.107119Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.107604Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.108063Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_litespeed_url`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.108663Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_litespeed_url` because it could not be opened.
2025-06-10T12:22:24.109035Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.109290Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.109617Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.109978Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_litespeed_url_file.ibd' OS error: 103
2025-06-10T12:22:24.110308Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.110603Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.111108Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_litespeed_url_file`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.111951Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_litespeed_url_file` because it could not be opened.
2025-06-10T12:22:24.112576Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.112969Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.113354Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.114000Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_options.ibd' OS error: 103
2025-06-10T12:22:24.114320Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.114840Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.115261Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.115865Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_options` because it could not be opened.
2025-06-10T12:22:24.116264Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.116590Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.116868Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.117253Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_post_views.ibd' OS error: 103
2025-06-10T12:22:24.117663Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.117912Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.118302Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_post_views`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.118927Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_post_views` because it could not be opened.
2025-06-10T12:22:24.119295Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.119687Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.119985Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.120731Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:24.121423Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.121912Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.122483Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.123111Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_postmeta` because it could not be opened.
2025-06-10T12:22:24.123628Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.123918Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.124237Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.124655Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_posts.ibd' OS error: 103
2025-06-10T12:22:24.124975Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.125273Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.125685Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.126284Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_posts` because it could not be opened.
2025-06-10T12:22:24.126800Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.127074Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.127466Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.128031Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:24.128631Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.128940Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.129485Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.130089Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:24.130718Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.130970Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.131304Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.131687Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:24.132010Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.132371Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.132827Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.133457Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:24.133907Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.134233Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.134532Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.134959Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:24.135319Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.135926Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.136497Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.137078Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_termmeta` because it could not be opened.
2025-06-10T12:22:24.137529Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.137786Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.138048Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.138532Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_terms.ibd' OS error: 103
2025-06-10T12:22:24.138859Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.139152Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.139576Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.140157Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_terms` because it could not be opened.
2025-06-10T12:22:24.140530Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.140797Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.141071Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.141483Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:24.141826Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.142295Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.142729Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.143348Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_usermeta` because it could not be opened.
2025-06-10T12:22:24.143714Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.143970Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.144356Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.144720Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_users.ibd' OS error: 103
2025-06-10T12:22:24.145019Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.145366Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.145758Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.146380Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_users` because it could not be opened.
2025-06-10T12:22:24.146762Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.147027Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.147366Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.147748Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_wc_admin_note_actions.ibd' OS error: 103
2025-06-10T12:22:24.148194Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.148474Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.148884Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_wc_admin_note_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.149601Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_wc_admin_note_actions` because it could not be opened.
2025-06-10T12:22:24.150052Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.150479Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.150742Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.151204Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_wc_admin_notes.ibd' OS error: 103
2025-06-10T12:22:24.151545Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.151789Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.152351Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_wc_admin_notes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.153657Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_wc_admin_notes` because it could not be opened.
2025-06-10T12:22:24.154582Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.155123Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.155432Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.155816Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_wc_category_lookup.ibd' OS error: 103
2025-06-10T12:22:24.156378Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.156699Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.157173Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_wc_category_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.157737Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_wc_category_lookup` because it could not be opened.
2025-06-10T12:22:24.158227Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.158485Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.158744Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.159194Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_wc_customer_lookup.ibd' OS error: 103
2025-06-10T12:22:24.159533Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.159826Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.160331Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_wc_customer_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.161030Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_wc_customer_lookup` because it could not be opened.
2025-06-10T12:22:24.161488Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.161767Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.162127Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.162695Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_wc_download_log.ibd' OS error: 103
2025-06-10T12:22:24.163189Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.163591Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.164088Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_wc_download_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.164636Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_wc_download_log` because it could not be opened.
2025-06-10T12:22:24.165136Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.165401Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.165661Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.166558Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_wc_order_coupon_lookup.ibd' OS error: 103
2025-06-10T12:22:24.167178Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.167434Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.168008Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_wc_order_coupon_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.168611Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_wc_order_coupon_lookup` because it could not be opened.
2025-06-10T12:22:24.169154Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.169450Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.169760Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.170304Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_wc_order_product_lookup.ibd' OS error: 103
2025-06-10T12:22:24.170752Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.171094Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.171558Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_wc_order_product_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.172192Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_wc_order_product_lookup` because it could not be opened.
2025-06-10T12:22:24.172698Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.173022Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.173511Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.173958Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_wc_order_stats.ibd' OS error: 103
2025-06-10T12:22:24.174313Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.174596Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.175051Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_wc_order_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.175644Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_wc_order_stats` because it could not be opened.
2025-06-10T12:22:24.176095Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.176373Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.176649Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.177069Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_wc_order_tax_lookup.ibd' OS error: 103
2025-06-10T12:22:24.177451Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.177729Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.178184Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_wc_order_tax_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.178790Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_wc_order_tax_lookup` because it could not be opened.
2025-06-10T12:22:24.179238Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.179509Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.179815Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.180221Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_wc_product_meta_lookup.ibd' OS error: 103
2025-06-10T12:22:24.180645Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.180960Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.181447Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_wc_product_meta_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.182156Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_wc_product_meta_lookup` because it could not be opened.
2025-06-10T12:22:24.182656Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.182995Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.183287Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.184014Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_wc_reserved_stock.ibd' OS error: 103
2025-06-10T12:22:24.184751Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.185037Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.186075Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_wc_reserved_stock`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.187203Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_wc_reserved_stock` because it could not be opened.
2025-06-10T12:22:24.187822Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.188085Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.188451Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.188835Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_wc_tax_rate_classes.ibd' OS error: 103
2025-06-10T12:22:24.189306Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.189725Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.190143Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_wc_tax_rate_classes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.190798Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_wc_tax_rate_classes` because it could not be opened.
2025-06-10T12:22:24.191317Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.191674Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.192010Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.192548Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_wc_webhooks.ibd' OS error: 103
2025-06-10T12:22:24.192908Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.193171Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.193725Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_wc_webhooks`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.194310Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_wc_webhooks` because it could not be opened.
2025-06-10T12:22:24.194879Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.195139Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.195474Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.195849Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_woocommerce_api_keys.ibd' OS error: 103
2025-06-10T12:22:24.196189Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.196662Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.197145Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_woocommerce_api_keys`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.197824Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_woocommerce_api_keys` because it could not be opened.
2025-06-10T12:22:24.198241Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.198580Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.198897Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.199365Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_woocommerce_attribute_taxonomies.ibd' OS error: 103
2025-06-10T12:22:24.199924Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.200199Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.200806Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_woocommerce_attribute_taxonomies`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.201628Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_woocommerce_attribute_taxonomies` because it could not be opened.
2025-06-10T12:22:24.202126Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.202415Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.202688Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.203074Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_woocommerce_downloadable_product_permissions.ibd' OS error: 103
2025-06-10T12:22:24.203539Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.203808Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.204226Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_woocommerce_downloadable_product_permissions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.204896Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_woocommerce_downloadable_product_permissions` because it could not be opened.
2025-06-10T12:22:24.205416Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.205689Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.205960Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.206409Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_woocommerce_log.ibd' OS error: 103
2025-06-10T12:22:24.206758Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.207022Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.207498Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_woocommerce_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.208160Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_woocommerce_log` because it could not be opened.
2025-06-10T12:22:24.208692Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.208948Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.209212Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.209813Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_woocommerce_order_itemmeta.ibd' OS error: 103
2025-06-10T12:22:24.210159Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.210515Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.211033Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_woocommerce_order_itemmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.211736Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_woocommerce_order_itemmeta` because it could not be opened.
2025-06-10T12:22:24.212154Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.212496Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.212761Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.213115Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_woocommerce_order_items.ibd' OS error: 103
2025-06-10T12:22:24.213526Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.214004Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.214575Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_woocommerce_order_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.215192Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_woocommerce_order_items` because it could not be opened.
2025-06-10T12:22:24.215738Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.215992Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.216246Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.216808Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_woocommerce_payment_tokenmeta.ibd' OS error: 103
2025-06-10T12:22:24.217185Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.217577Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.218875Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_woocommerce_payment_tokenmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.220401Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_woocommerce_payment_tokenmeta` because it could not be opened.
2025-06-10T12:22:24.220958Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.221258Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.221536Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.221969Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_woocommerce_payment_tokens.ibd' OS error: 103
2025-06-10T12:22:24.222335Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.222596Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.223077Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_woocommerce_payment_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.223720Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_woocommerce_payment_tokens` because it could not be opened.
2025-06-10T12:22:24.224168Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.224439Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.224759Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.225154Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_woocommerce_sessions.ibd' OS error: 103
2025-06-10T12:22:24.225532Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.226004Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.226495Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_woocommerce_sessions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.227347Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_woocommerce_sessions` because it could not be opened.
2025-06-10T12:22:24.228199Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.228694Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.229238Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.229869Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_woocommerce_shipping_zone_locations.ibd' OS error: 103
2025-06-10T12:22:24.230343Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.230721Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.231200Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_woocommerce_shipping_zone_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.231964Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_woocommerce_shipping_zone_locations` because it could not be opened.
2025-06-10T12:22:24.232454Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.232767Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.233046Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.233437Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_woocommerce_shipping_zone_methods.ibd' OS error: 103
2025-06-10T12:22:24.233899Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.234172Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.234660Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_woocommerce_shipping_zone_methods`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.235307Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_woocommerce_shipping_zone_methods` because it could not be opened.
2025-06-10T12:22:24.235821Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.236092Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.236370Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.236802Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_woocommerce_shipping_zones.ibd' OS error: 103
2025-06-10T12:22:24.237171Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.237437Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.237888Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_woocommerce_shipping_zones`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.238517Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_woocommerce_shipping_zones` because it could not be opened.
2025-06-10T12:22:24.238999Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.239299Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.239576Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.240001Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_woocommerce_tax_rate_locations.ibd' OS error: 103
2025-06-10T12:22:24.240379Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.240682Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.241123Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_woocommerce_tax_rate_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.241901Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_woocommerce_tax_rate_locations` because it could not be opened.
2025-06-10T12:22:24.242444Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.242900Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.243343Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.243901Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_woocommerce_tax_rates.ibd' OS error: 103
2025-06-10T12:22:24.244292Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.244558Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.245015Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_woocommerce_tax_rates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.245759Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_woocommerce_tax_rates` because it could not be opened.
2025-06-10T12:22:24.246348Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.246680Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.246998Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.247505Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_wpmailsmtp_debug_events.ibd' OS error: 103
2025-06-10T12:22:24.248008Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.248412Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.249059Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_wpmailsmtp_debug_events`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.249804Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_wpmailsmtp_debug_events` because it could not be opened.
2025-06-10T12:22:24.250292Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.250621Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.250946Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.251444Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_wpmailsmtp_tasks_meta.ibd' OS error: 103
2025-06-10T12:22:24.251806Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.252094Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.252535Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_wpmailsmtp_tasks_meta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.253198Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_wpmailsmtp_tasks_meta` because it could not be opened.
2025-06-10T12:22:24.253700Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.253965Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.254278Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.254659Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:24.255074Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.255396Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.255800Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.256519Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:24.257727Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.258406Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.258693Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.259341Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:24.259704Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.259996Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.260423Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.261058Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:24.261601Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.262075Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.262382Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.262757Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:24.263154Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.263411Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.263878Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.264519Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:24.265092Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.265432Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.265741Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.266221Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_enpro1\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:24.266584Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.266924Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.267397Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_enpro1/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.268138Z 0 [Warning] InnoDB: Ignoring tablespace `client_enpro1/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:24.268664Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.269038Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.269334Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.269753Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_actionscheduler_actions.ibd' OS error: 103
2025-06-10T12:22:24.270181Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.270501Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.270945Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_actionscheduler_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.271543Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_actionscheduler_actions` because it could not be opened.
2025-06-10T12:22:24.284225Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.284737Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.285178Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.285596Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_actionscheduler_claims.ibd' OS error: 103
2025-06-10T12:22:24.286059Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.286313Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.286711Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_actionscheduler_claims`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.287402Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_actionscheduler_claims` because it could not be opened.
2025-06-10T12:22:24.287969Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.288266Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.288571Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.289020Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_actionscheduler_groups.ibd' OS error: 103
2025-06-10T12:22:24.289363Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.289614Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.290103Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_actionscheduler_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.290702Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_actionscheduler_groups` because it could not be opened.
2025-06-10T12:22:24.291218Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.291602Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.291959Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.292346Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_actionscheduler_logs.ibd' OS error: 103
2025-06-10T12:22:24.292783Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.293175Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.293627Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_actionscheduler_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.294289Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_actionscheduler_logs` because it could not be opened.
2025-06-10T12:22:24.294763Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.295056Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.295334Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.295830Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_chaty_contact_form_leads.ibd' OS error: 103
2025-06-10T12:22:24.296469Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.296798Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.297191Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_chaty_contact_form_leads`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.297858Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_chaty_contact_form_leads` because it could not be opened.
2025-06-10T12:22:24.298283Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.298565Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.298828Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.299568Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:24.300085Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.300346Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.300761Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.301425Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:24.301832Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.302178Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.302436Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.302807Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_comments.ibd' OS error: 103
2025-06-10T12:22:24.303218Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.303468Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.303876Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.304538Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_comments` because it could not be opened.
2025-06-10T12:22:24.305072Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.305351Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.305617Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.306140Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:24.306652Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.306964Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.307432Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.307943Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_fbv` because it could not be opened.
2025-06-10T12:22:24.308532Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.308830Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.309198Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.309661Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:24.310151Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.310436Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.310824Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.311525Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:24.312008Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.312384Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.312663Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.313163Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_itsec_bans.ibd' OS error: 103
2025-06-10T12:22:24.313594Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.313838Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.314365Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_itsec_bans`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.314891Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_itsec_bans` because it could not be opened.
2025-06-10T12:22:24.315396Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.315646Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.315896Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.316475Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_itsec_dashboard_events.ibd' OS error: 103
2025-06-10T12:22:24.316805Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.317194Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.317587Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_itsec_dashboard_events`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.318289Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_itsec_dashboard_events` because it could not be opened.
2025-06-10T12:22:24.318767Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.319097Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.319374Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.319736Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_itsec_distributed_storage.ibd' OS error: 103
2025-06-10T12:22:24.320152Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.320403Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.320793Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_itsec_distributed_storage`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.321486Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_itsec_distributed_storage` because it could not be opened.
2025-06-10T12:22:24.321875Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.322229Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.322538Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.322953Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_itsec_fingerprints.ibd' OS error: 103
2025-06-10T12:22:24.323310Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.323575Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.324072Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_itsec_fingerprints`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.324811Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_itsec_fingerprints` because it could not be opened.
2025-06-10T12:22:24.325327Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.325593Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.325856Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.326344Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_itsec_geolocation_cache.ibd' OS error: 103
2025-06-10T12:22:24.326703Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.327015Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.327419Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_itsec_geolocation_cache`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.328426Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_itsec_geolocation_cache` because it could not be opened.
2025-06-10T12:22:24.329391Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.329729Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.330386Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.330780Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_itsec_lockouts.ibd' OS error: 103
2025-06-10T12:22:24.331197Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.331507Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.331978Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_itsec_lockouts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.332719Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_itsec_lockouts` because it could not be opened.
2025-06-10T12:22:24.333150Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.333444Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.333724Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.334095Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_itsec_logs.ibd' OS error: 103
2025-06-10T12:22:24.334496Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.334788Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.335196Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_itsec_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.336046Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_itsec_logs` because it could not be opened.
2025-06-10T12:22:24.336594Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.336858Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.337121Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.337599Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_itsec_mutexes.ibd' OS error: 103
2025-06-10T12:22:24.338018Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.338332Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.339035Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_itsec_mutexes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.339767Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_itsec_mutexes` because it could not be opened.
2025-06-10T12:22:24.340190Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.340493Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.340768Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.341152Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_itsec_opaque_tokens.ibd' OS error: 103
2025-06-10T12:22:24.341521Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.341785Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.342199Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_itsec_opaque_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.342832Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_itsec_opaque_tokens` because it could not be opened.
2025-06-10T12:22:24.343244Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.343536Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.343808Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.344188Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_itsec_temp.ibd' OS error: 103
2025-06-10T12:22:24.344548Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.344810Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.345425Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_itsec_temp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.346008Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_itsec_temp` because it could not be opened.
2025-06-10T12:22:24.346436Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.346743Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.347006Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.347399Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_itsec_user_groups.ibd' OS error: 103
2025-06-10T12:22:24.347744Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.347994Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.348442Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_itsec_user_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.349083Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_itsec_user_groups` because it could not be opened.
2025-06-10T12:22:24.349501Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.349801Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.350060Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.350570Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_kbp_countdown_entry.ibd' OS error: 103
2025-06-10T12:22:24.350913Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.351162Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.351961Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_kbp_countdown_entry`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.352608Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_kbp_countdown_entry` because it could not be opened.
2025-06-10T12:22:24.352998Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.353253Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.353667Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.354037Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_kbp_form_entry.ibd' OS error: 103
2025-06-10T12:22:24.354429Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.354752Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.355133Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_kbp_form_entry`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.355791Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_kbp_form_entry` because it could not be opened.
2025-06-10T12:22:24.356194Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.356549Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.356844Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.357237Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_kbp_form_entrymeta.ibd' OS error: 103
2025-06-10T12:22:24.357705Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.357989Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.358535Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_kbp_form_entrymeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.359164Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_kbp_form_entrymeta` because it could not be opened.
2025-06-10T12:22:24.360167Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.360451Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.361399Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.361843Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_links.ibd' OS error: 103
2025-06-10T12:22:24.362238Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.362532Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.362955Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.363537Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_links` because it could not be opened.
2025-06-10T12:22:24.363943Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.364245Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.364515Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.364894Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_litespeed_url.ibd' OS error: 103
2025-06-10T12:22:24.365262Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.365596Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.366060Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_litespeed_url`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.366693Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_litespeed_url` because it could not be opened.
2025-06-10T12:22:24.367239Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.367522Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.367782Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.368237Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_litespeed_url_file.ibd' OS error: 103
2025-06-10T12:22:24.368669Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.368980Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.369525Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_litespeed_url_file`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.370156Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_litespeed_url_file` because it could not be opened.
2025-06-10T12:22:24.370598Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.370861Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.371214Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.371595Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_options.ibd' OS error: 103
2025-06-10T12:22:24.371906Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.372226Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.372619Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.373216Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_options` because it could not be opened.
2025-06-10T12:22:24.373615Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.373986Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.374367Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.374730Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_post_views.ibd' OS error: 103
2025-06-10T12:22:24.375060Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.375363Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.375754Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_post_views`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.376401Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_post_views` because it could not be opened.
2025-06-10T12:22:24.376768Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.377022Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.377344Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.377706Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:24.378014Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.378357Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.378761Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.379380Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_postmeta` because it could not be opened.
2025-06-10T12:22:24.379734Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.379987Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.380365Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.380735Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_posts.ibd' OS error: 103
2025-06-10T12:22:24.381089Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.381408Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.381803Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.382495Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_posts` because it could not be opened.
2025-06-10T12:22:24.382845Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.383175Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.383444Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.383804Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:24.384286Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.384593Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.384999Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.385835Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:24.386372Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.386643Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.386918Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.387397Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:24.387735Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.387984Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.388473Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.389126Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:24.389536Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.389802Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.390111Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.390497Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:24.390821Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.391193Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.391598Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.393715Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_termmeta` because it could not be opened.
2025-06-10T12:22:24.394537Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.394817Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.395093Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.395531Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_terms.ibd' OS error: 103
2025-06-10T12:22:24.395859Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.396123Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.396583Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.397176Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_terms` because it could not be opened.
2025-06-10T12:22:24.397846Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.398146Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.398454Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.398853Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:24.399325Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.399672Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.400098Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.400942Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_usermeta` because it could not be opened.
2025-06-10T12:22:24.401843Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.402214Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.402568Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.402962Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_users.ibd' OS error: 103
2025-06-10T12:22:24.403284Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.403610Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.404053Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.404762Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_users` because it could not be opened.
2025-06-10T12:22:24.405213Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.405515Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.405794Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.406186Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_wc_admin_note_actions.ibd' OS error: 103
2025-06-10T12:22:24.406576Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.406843Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.407268Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_wc_admin_note_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.407920Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_wc_admin_note_actions` because it could not be opened.
2025-06-10T12:22:24.408364Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.408660Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.408933Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.409321Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_wc_admin_notes.ibd' OS error: 103
2025-06-10T12:22:24.409690Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.409966Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.410382Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_wc_admin_notes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.410996Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_wc_admin_notes` because it could not be opened.
2025-06-10T12:22:24.411415Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.411705Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.411979Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.412367Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_wc_category_lookup.ibd' OS error: 103
2025-06-10T12:22:24.412749Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.413016Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.413469Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_wc_category_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.414062Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_wc_category_lookup` because it could not be opened.
2025-06-10T12:22:24.414499Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.414768Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.415041Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.415468Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_wc_customer_lookup.ibd' OS error: 103
2025-06-10T12:22:24.415824Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.416091Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.416571Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_wc_customer_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.417183Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_wc_customer_lookup` because it could not be opened.
2025-06-10T12:22:24.417637Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.417910Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.418185Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.418605Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_wc_download_log.ibd' OS error: 103
2025-06-10T12:22:24.418973Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.419271Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.419830Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_wc_download_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.420516Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_wc_download_log` because it could not be opened.
2025-06-10T12:22:24.421007Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.421283Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.421579Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.421967Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_wc_order_coupon_lookup.ibd' OS error: 103
2025-06-10T12:22:24.422326Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.422633Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.423053Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_wc_order_coupon_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.423927Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_wc_order_coupon_lookup` because it could not be opened.
2025-06-10T12:22:24.425317Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.426113Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.426540Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.426967Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_wc_order_product_lookup.ibd' OS error: 103
2025-06-10T12:22:24.427531Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.427869Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.428296Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_wc_order_product_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.428959Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_wc_order_product_lookup` because it could not be opened.
2025-06-10T12:22:24.429447Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.429724Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.429995Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.430418Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_wc_order_stats.ibd' OS error: 103
2025-06-10T12:22:24.430772Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.431043Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.431514Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_wc_order_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.432124Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_wc_order_stats` because it could not be opened.
2025-06-10T12:22:24.432627Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.432901Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.433188Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.433648Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_wc_order_tax_lookup.ibd' OS error: 103
2025-06-10T12:22:24.434005Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.434453Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.434907Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_wc_order_tax_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.435537Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_wc_order_tax_lookup` because it could not be opened.
2025-06-10T12:22:24.436000Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.436277Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.436630Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.437025Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_wc_product_meta_lookup.ibd' OS error: 103
2025-06-10T12:22:24.437441Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.437715Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.438127Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_wc_product_meta_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.438765Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_wc_product_meta_lookup` because it could not be opened.
2025-06-10T12:22:24.439196Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.439503Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.439772Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.440152Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_wc_reserved_stock.ibd' OS error: 103
2025-06-10T12:22:24.440604Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.441005Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.441453Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_wc_reserved_stock`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.442040Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_wc_reserved_stock` because it could not be opened.
2025-06-10T12:22:24.442502Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.442773Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.443117Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.443609Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_wc_tax_rate_classes.ibd' OS error: 103
2025-06-10T12:22:24.443964Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.444227Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.444688Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_wc_tax_rate_classes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.445278Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_wc_tax_rate_classes` because it could not be opened.
2025-06-10T12:22:24.445858Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.446192Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.446516Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.447067Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_wc_webhooks.ibd' OS error: 103
2025-06-10T12:22:24.447441Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.447708Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.448116Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_wc_webhooks`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.448768Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_wc_webhooks` because it could not be opened.
2025-06-10T12:22:24.449173Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.449501Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.449774Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.450154Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_woocommerce_api_keys.ibd' OS error: 103
2025-06-10T12:22:24.450625Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.450895Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.451324Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_woocommerce_api_keys`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.452011Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_woocommerce_api_keys` because it could not be opened.
2025-06-10T12:22:24.452555Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.452809Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.453068Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.453589Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_woocommerce_attribute_taxonomies.ibd' OS error: 103
2025-06-10T12:22:24.453974Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.454224Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.454697Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_woocommerce_attribute_taxonomies`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.455356Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_woocommerce_attribute_taxonomies` because it could not be opened.
2025-06-10T12:22:24.455816Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.456067Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.456422Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.456790Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_woocommerce_downloadable_product_permissions.ibd' OS error: 103
2025-06-10T12:22:24.457186Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.457560Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.457956Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_woocommerce_downloadable_product_permissions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.458680Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_woocommerce_downloadable_product_permissions` because it could not be opened.
2025-06-10T12:22:24.459122Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.459538Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.459817Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.460180Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_woocommerce_log.ibd' OS error: 103
2025-06-10T12:22:24.460555Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.460806Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.461201Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_woocommerce_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.461844Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_woocommerce_log` because it could not be opened.
2025-06-10T12:22:24.462224Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.462566Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.462826Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.463192Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_woocommerce_order_itemmeta.ibd' OS error: 103
2025-06-10T12:22:24.463673Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.464112Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.464717Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_woocommerce_order_itemmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.465381Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_woocommerce_order_itemmeta` because it could not be opened.
2025-06-10T12:22:24.465923Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.466185Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.466521Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.466909Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_woocommerce_order_items.ibd' OS error: 103
2025-06-10T12:22:24.467268Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.467575Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.467971Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_woocommerce_order_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.468680Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_woocommerce_order_items` because it could not be opened.
2025-06-10T12:22:24.469110Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.469449Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.469722Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.470096Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_woocommerce_payment_tokenmeta.ibd' OS error: 103
2025-06-10T12:22:24.470520Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.470771Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.471172Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_woocommerce_payment_tokenmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.471912Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_woocommerce_payment_tokenmeta` because it could not be opened.
2025-06-10T12:22:24.472562Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.473006Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.473271Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.473712Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_woocommerce_payment_tokens.ibd' OS error: 103
2025-06-10T12:22:24.474124Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.474431Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.474879Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_woocommerce_payment_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.475519Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_woocommerce_payment_tokens` because it could not be opened.
2025-06-10T12:22:24.475970Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.476256Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.476578Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.477076Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_woocommerce_sessions.ibd' OS error: 103
2025-06-10T12:22:24.477454Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.477718Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.478142Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_woocommerce_sessions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.479025Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_woocommerce_sessions` because it could not be opened.
2025-06-10T12:22:24.479561Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.479823Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.480083Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.480601Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_woocommerce_shipping_zone_locations.ibd' OS error: 103
2025-06-10T12:22:24.480993Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.481321Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.481776Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_woocommerce_shipping_zone_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.482543Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_woocommerce_shipping_zone_locations` because it could not be opened.
2025-06-10T12:22:24.483013Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.483423Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.483699Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.484064Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_woocommerce_shipping_zone_methods.ibd' OS error: 103
2025-06-10T12:22:24.484704Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.485020Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.485502Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_woocommerce_shipping_zone_methods`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.486349Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_woocommerce_shipping_zone_methods` because it could not be opened.
2025-06-10T12:22:24.486819Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.487073Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.487490Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.487965Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_woocommerce_shipping_zones.ibd' OS error: 103
2025-06-10T12:22:24.488529Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.488875Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.489358Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_woocommerce_shipping_zones`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.489992Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_woocommerce_shipping_zones` because it could not be opened.
2025-06-10T12:22:24.490493Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.490747Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.491007Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.491445Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_woocommerce_tax_rate_locations.ibd' OS error: 103
2025-06-10T12:22:24.491873Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.492126Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.492788Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_woocommerce_tax_rate_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.493545Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_woocommerce_tax_rate_locations` because it could not be opened.
2025-06-10T12:22:24.494028Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.494317Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.494593Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.494974Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_woocommerce_tax_rates.ibd' OS error: 103
2025-06-10T12:22:24.495408Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.495672Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.496091Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_woocommerce_tax_rates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.496755Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_woocommerce_tax_rates` because it could not be opened.
2025-06-10T12:22:24.497213Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.497485Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.497756Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.498140Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_wpmailsmtp_debug_events.ibd' OS error: 103
2025-06-10T12:22:24.498766Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.499059Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.499556Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_wpmailsmtp_debug_events`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.500132Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_wpmailsmtp_debug_events` because it could not be opened.
2025-06-10T12:22:24.500624Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.500889Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.501254Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.501639Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_wpmailsmtp_tasks_meta.ibd' OS error: 103
2025-06-10T12:22:24.501989Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.502447Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.502846Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_wpmailsmtp_tasks_meta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.503481Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_wpmailsmtp_tasks_meta` because it could not be opened.
2025-06-10T12:22:24.503883Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.504575Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.505813Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.506232Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:24.506988Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.507254Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.507677Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.508333Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:24.508788Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.509120Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.509393Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.509776Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:24.510206Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.510528Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.511028Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.511657Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:24.512330Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.512615Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.512912Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.513391Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:24.513734Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.514109Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.514645Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.515281Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:24.515684Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.516009Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.516275Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.516646Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:24.517130Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.517398Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.517877Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.518590Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:24.519028Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.519438Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.519734Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.520172Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_yoast_indexable.ibd' OS error: 103
2025-06-10T12:22:24.520518Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.520780Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.521236Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_yoast_indexable`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.521810Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_yoast_indexable` because it could not be opened.
2025-06-10T12:22:24.522251Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.522519Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.522793Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.523216Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_yoast_indexable_hierarchy.ibd' OS error: 103
2025-06-10T12:22:24.523580Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.523853Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.524290Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_yoast_indexable_hierarchy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.525108Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_yoast_indexable_hierarchy` because it could not be opened.
2025-06-10T12:22:24.525534Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.525802Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.526151Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.526556Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_yoast_migrations.ibd' OS error: 103
2025-06-10T12:22:24.526944Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.527213Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.527637Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_yoast_migrations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.528293Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_yoast_migrations` because it could not be opened.
2025-06-10T12:22:24.528696Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.529050Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.529494Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.529936Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_yoast_primary_term.ibd' OS error: 103
2025-06-10T12:22:24.530288Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.530552Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.531007Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_yoast_primary_term`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.531617Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_yoast_primary_term` because it could not be opened.
2025-06-10T12:22:24.532090Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.532371Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.532648Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.533095Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_fumeng1\wp_yoast_seo_links.ibd' OS error: 103
2025-06-10T12:22:24.533445Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.533709Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.534224Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_fumeng1/wp_yoast_seo_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.534875Z 0 [Warning] InnoDB: Ignoring tablespace `client_fumeng1/wp_yoast_seo_links` because it could not be opened.
2025-06-10T12:22:24.535591Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.535975Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.536393Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.537201Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_hcwong\wp_actionscheduler_actions.ibd' OS error: 103
2025-06-10T12:22:24.537627Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.538184Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.538912Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_hcwong/wp_actionscheduler_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.539559Z 0 [Warning] InnoDB: Ignoring tablespace `client_hcwong/wp_actionscheduler_actions` because it could not be opened.
2025-06-10T12:22:24.540022Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.540282Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.540628Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.541014Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_hcwong\wp_actionscheduler_claims.ibd' OS error: 103
2025-06-10T12:22:24.541369Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.541739Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.542145Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_hcwong/wp_actionscheduler_claims`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.542860Z 0 [Warning] InnoDB: Ignoring tablespace `client_hcwong/wp_actionscheduler_claims` because it could not be opened.
2025-06-10T12:22:24.543331Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.543760Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.544042Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.544467Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_hcwong\wp_actionscheduler_groups.ibd' OS error: 103
2025-06-10T12:22:24.544919Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.545225Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.545821Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_hcwong/wp_actionscheduler_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.546624Z 0 [Warning] InnoDB: Ignoring tablespace `client_hcwong/wp_actionscheduler_groups` because it could not be opened.
2025-06-10T12:22:24.547051Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.547306Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.547684Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.548044Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_hcwong\wp_actionscheduler_logs.ibd' OS error: 103
2025-06-10T12:22:24.548377Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.548713Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.549103Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_hcwong/wp_actionscheduler_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.549775Z 0 [Warning] InnoDB: Ignoring tablespace `client_hcwong/wp_actionscheduler_logs` because it could not be opened.
2025-06-10T12:22:24.550153Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.550436Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.550777Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.551139Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_hcwong\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:24.551752Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.552053Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.552486Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_hcwong/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.553122Z 0 [Warning] InnoDB: Ignoring tablespace `client_hcwong/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:24.553547Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.553825Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.554086Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.554480Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_hcwong\wp_comments.ibd' OS error: 103
2025-06-10T12:22:24.554824Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.555076Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.555521Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_hcwong/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.556074Z 0 [Warning] InnoDB: Ignoring tablespace `client_hcwong/wp_comments` because it could not be opened.
2025-06-10T12:22:24.556422Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.556783Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.557042Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.557412Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_hcwong\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:24.557819Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.558072Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.558502Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_hcwong/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.559059Z 0 [Warning] InnoDB: Ignoring tablespace `client_hcwong/wp_fbv` because it could not be opened.
2025-06-10T12:22:24.559400Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.559709Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.559969Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.560354Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_hcwong\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:24.560810Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.561068Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.561662Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_hcwong/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.562267Z 0 [Warning] InnoDB: Ignoring tablespace `client_hcwong/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:24.562753Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.563018Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.563292Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.563709Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_hcwong\wp_kbp_countdown_entry.ibd' OS error: 103
2025-06-10T12:22:24.564063Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.564335Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.564893Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_hcwong/wp_kbp_countdown_entry`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.565507Z 0 [Warning] InnoDB: Ignoring tablespace `client_hcwong/wp_kbp_countdown_entry` because it could not be opened.
2025-06-10T12:22:24.566001Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.566254Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.566607Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.566973Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_hcwong\wp_kbp_form_entry.ibd' OS error: 103
2025-06-10T12:22:24.567319Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.568099Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.568693Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_hcwong/wp_kbp_form_entry`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.569996Z 0 [Warning] InnoDB: Ignoring tablespace `client_hcwong/wp_kbp_form_entry` because it could not be opened.
2025-06-10T12:22:24.570520Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.570814Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.571091Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.571500Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_hcwong\wp_kbp_form_entrymeta.ibd' OS error: 103
2025-06-10T12:22:24.571854Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.572368Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.572794Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_hcwong/wp_kbp_form_entrymeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.573530Z 0 [Warning] InnoDB: Ignoring tablespace `client_hcwong/wp_kbp_form_entrymeta` because it could not be opened.
2025-06-10T12:22:24.574108Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.574479Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.574807Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.575261Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_hcwong\wp_links.ibd' OS error: 103
2025-06-10T12:22:24.575589Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.575842Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.576354Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_hcwong/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.576923Z 0 [Warning] InnoDB: Ignoring tablespace `client_hcwong/wp_links` because it could not be opened.
2025-06-10T12:22:24.577572Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.577834Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.578107Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.578708Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_hcwong\wp_options.ibd' OS error: 103
2025-06-10T12:22:24.579044Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.579368Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.579822Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_hcwong/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.580408Z 0 [Warning] InnoDB: Ignoring tablespace `client_hcwong/wp_options` because it could not be opened.
2025-06-10T12:22:24.580794Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.581047Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.581378Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.581745Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_hcwong\wp_post_views.ibd' OS error: 103
2025-06-10T12:22:24.582058Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.582360Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.582773Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_hcwong/wp_post_views`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.583371Z 0 [Warning] InnoDB: Ignoring tablespace `client_hcwong/wp_post_views` because it could not be opened.
2025-06-10T12:22:24.583780Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.584044Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.584346Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.584728Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_hcwong\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:24.585050Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.585342Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.585957Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_hcwong/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.586561Z 0 [Warning] InnoDB: Ignoring tablespace `client_hcwong/wp_postmeta` because it could not be opened.
2025-06-10T12:22:24.586968Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.587310Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.587575Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.587942Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_hcwong\wp_posts.ibd' OS error: 103
2025-06-10T12:22:24.588374Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.588625Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.589021Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_hcwong/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.589684Z 0 [Warning] InnoDB: Ignoring tablespace `client_hcwong/wp_posts` because it could not be opened.
2025-06-10T12:22:24.590040Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.590374Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.590632Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.590999Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_hcwong\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:24.591422Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.591802Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.592317Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_hcwong/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.592876Z 0 [Warning] InnoDB: Ignoring tablespace `client_hcwong/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:24.593416Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.593669Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.594069Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.594586Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_hcwong\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:24.594901Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.595273Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.595681Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_hcwong/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.596342Z 0 [Warning] InnoDB: Ignoring tablespace `client_hcwong/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:24.596815Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.597159Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.597444Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.597942Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_hcwong\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:24.598403Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.598662Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.599136Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_hcwong/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.599721Z 0 [Warning] InnoDB: Ignoring tablespace `client_hcwong/wp_termmeta` because it could not be opened.
2025-06-10T12:22:24.600202Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.600504Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.600896Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.601360Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_hcwong\wp_terms.ibd' OS error: 103
2025-06-10T12:22:24.602221Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.603011Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.603485Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_hcwong/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.604047Z 0 [Warning] InnoDB: Ignoring tablespace `client_hcwong/wp_terms` because it could not be opened.
2025-06-10T12:22:24.604544Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.604898Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.605327Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.605782Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_hcwong\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:24.606096Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.606344Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.606928Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_hcwong/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.607520Z 0 [Warning] InnoDB: Ignoring tablespace `client_hcwong/wp_usermeta` because it could not be opened.
2025-06-10T12:22:24.608066Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.608364Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.608704Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.609071Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_hcwong\wp_users.ibd' OS error: 103
2025-06-10T12:22:24.609470Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.609745Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.610153Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_hcwong/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.610850Z 0 [Warning] InnoDB: Ignoring tablespace `client_hcwong/wp_users` because it could not be opened.
2025-06-10T12:22:24.611459Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.611795Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.612054Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.612511Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_hcwong\wp_wc_admin_note_actions.ibd' OS error: 103
2025-06-10T12:22:24.612846Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.613092Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.613523Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_hcwong/wp_wc_admin_note_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.614090Z 0 [Warning] InnoDB: Ignoring tablespace `client_hcwong/wp_wc_admin_note_actions` because it could not be opened.
2025-06-10T12:22:24.614588Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.614838Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.615091Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.615510Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_hcwong\wp_wc_admin_notes.ibd' OS error: 103
2025-06-10T12:22:24.615830Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.616079Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.616534Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_hcwong/wp_wc_admin_notes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.617081Z 0 [Warning] InnoDB: Ignoring tablespace `client_hcwong/wp_wc_admin_notes` because it could not be opened.
2025-06-10T12:22:24.617500Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.617747Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.618005Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.618527Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_hcwong\wp_wc_category_lookup.ibd' OS error: 103
2025-06-10T12:22:24.618869Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.619114Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.619584Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_hcwong/wp_wc_category_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.620136Z 0 [Warning] InnoDB: Ignoring tablespace `client_hcwong/wp_wc_category_lookup` because it could not be opened.
2025-06-10T12:22:24.620576Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.620905Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.621161Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.621571Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_hcwong\wp_wc_customer_lookup.ibd' OS error: 103
2025-06-10T12:22:24.621900Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.622147Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.622623Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_hcwong/wp_wc_customer_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.623228Z 0 [Warning] InnoDB: Ignoring tablespace `client_hcwong/wp_wc_customer_lookup` because it could not be opened.
2025-06-10T12:22:24.623673Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.623921Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.624179Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.624841Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_hcwong\wp_wc_download_log.ibd' OS error: 103
2025-06-10T12:22:24.625191Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.625528Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.625935Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_hcwong/wp_wc_download_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.626648Z 0 [Warning] InnoDB: Ignoring tablespace `client_hcwong/wp_wc_download_log` because it could not be opened.
2025-06-10T12:22:24.627057Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.627314Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.627676Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.628045Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_hcwong\wp_wc_order_coupon_lookup.ibd' OS error: 103
2025-06-10T12:22:24.628484Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.628751Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.629175Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_hcwong/wp_wc_order_coupon_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.629888Z 0 [Warning] InnoDB: Ignoring tablespace `client_hcwong/wp_wc_order_coupon_lookup` because it could not be opened.
2025-06-10T12:22:24.630426Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.630910Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.631196Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.631615Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_hcwong\wp_wc_order_product_lookup.ibd' OS error: 103
2025-06-10T12:22:24.631955Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.632204Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.632780Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_hcwong/wp_wc_order_product_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.633862Z 0 [Warning] InnoDB: Ignoring tablespace `client_hcwong/wp_wc_order_product_lookup` because it could not be opened.
2025-06-10T12:22:24.634762Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.635030Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.635356Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.635739Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_hcwong\wp_wc_order_stats.ibd' OS error: 103
2025-06-10T12:22:24.636083Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.636409Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.636821Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_hcwong/wp_wc_order_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.637459Z 0 [Warning] InnoDB: Ignoring tablespace `client_hcwong/wp_wc_order_stats` because it could not be opened.
2025-06-10T12:22:24.637886Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.638181Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.638510Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.638894Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_hcwong\wp_wc_order_tax_lookup.ibd' OS error: 103
2025-06-10T12:22:24.639303Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.639579Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.639986Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_hcwong/wp_wc_order_tax_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.640648Z 0 [Warning] InnoDB: Ignoring tablespace `client_hcwong/wp_wc_order_tax_lookup` because it could not be opened.
2025-06-10T12:22:24.641096Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.641569Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.641898Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.642321Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_hcwong\wp_wc_product_meta_lookup.ibd' OS error: 103
2025-06-10T12:22:24.642683Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.642947Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.643441Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_hcwong/wp_wc_product_meta_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.644054Z 0 [Warning] InnoDB: Ignoring tablespace `client_hcwong/wp_wc_product_meta_lookup` because it could not be opened.
2025-06-10T12:22:24.644699Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.644949Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.645254Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.645634Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_hcwong\wp_wc_reserved_stock.ibd' OS error: 103
2025-06-10T12:22:24.645978Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.646374Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.646896Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_hcwong/wp_wc_reserved_stock`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.647616Z 0 [Warning] InnoDB: Ignoring tablespace `client_hcwong/wp_wc_reserved_stock` because it could not be opened.
2025-06-10T12:22:24.648064Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.648378Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.648659Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.649048Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_hcwong\wp_wc_tax_rate_classes.ibd' OS error: 103
2025-06-10T12:22:24.649442Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.649724Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.650164Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_hcwong/wp_wc_tax_rate_classes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.650785Z 0 [Warning] InnoDB: Ignoring tablespace `client_hcwong/wp_wc_tax_rate_classes` because it could not be opened.
2025-06-10T12:22:24.651458Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.651747Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.652023Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.652493Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_hcwong\wp_wc_webhooks.ibd' OS error: 103
2025-06-10T12:22:24.652839Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.653111Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.653643Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_hcwong/wp_wc_webhooks`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.654357Z 0 [Warning] InnoDB: Ignoring tablespace `client_hcwong/wp_wc_webhooks` because it could not be opened.
2025-06-10T12:22:24.655006Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.655373Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.655687Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.656167Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_hcwong\wp_woocommerce_api_keys.ibd' OS error: 103
2025-06-10T12:22:24.656566Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.656910Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.657411Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_hcwong/wp_woocommerce_api_keys`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.658080Z 0 [Warning] InnoDB: Ignoring tablespace `client_hcwong/wp_woocommerce_api_keys` because it could not be opened.
2025-06-10T12:22:24.658594Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.659235Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.659596Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.659995Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_hcwong\wp_woocommerce_attribute_taxonomies.ibd' OS error: 103
2025-06-10T12:22:24.660500Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.660807Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.661309Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_hcwong/wp_woocommerce_attribute_taxonomies`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.661957Z 0 [Warning] InnoDB: Ignoring tablespace `client_hcwong/wp_woocommerce_attribute_taxonomies` because it could not be opened.
2025-06-10T12:22:24.662521Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.662793Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.663064Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.663517Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_hcwong\wp_woocommerce_downloadable_product_permissions.ibd' OS error: 103
2025-06-10T12:22:24.663945Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.664394Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.664965Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_hcwong/wp_woocommerce_downloadable_product_permissions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.665756Z 0 [Warning] InnoDB: Ignoring tablespace `client_hcwong/wp_woocommerce_downloadable_product_permissions` because it could not be opened.
2025-06-10T12:22:24.666748Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.667102Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.667449Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.667852Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_hcwong\wp_woocommerce_log.ibd' OS error: 103
2025-06-10T12:22:24.668324Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.668609Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.669061Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_hcwong/wp_woocommerce_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.669687Z 0 [Warning] InnoDB: Ignoring tablespace `client_hcwong/wp_woocommerce_log` because it could not be opened.
2025-06-10T12:22:24.670229Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.670662Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.670964Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.671545Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_hcwong\wp_woocommerce_order_itemmeta.ibd' OS error: 103
2025-06-10T12:22:24.671944Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.672333Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.672798Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_hcwong/wp_woocommerce_order_itemmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.673628Z 0 [Warning] InnoDB: Ignoring tablespace `client_hcwong/wp_woocommerce_order_itemmeta` because it could not be opened.
2025-06-10T12:22:24.674316Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.674810Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.675167Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.675663Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_hcwong\wp_woocommerce_order_items.ibd' OS error: 103
2025-06-10T12:22:24.676060Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.676456Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.676876Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_hcwong/wp_woocommerce_order_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.677562Z 0 [Warning] InnoDB: Ignoring tablespace `client_hcwong/wp_woocommerce_order_items` because it could not be opened.
2025-06-10T12:22:24.678020Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.678367Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.678637Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.679249Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_hcwong\wp_woocommerce_payment_tokenmeta.ibd' OS error: 103
2025-06-10T12:22:24.679639Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.679902Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.680402Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_hcwong/wp_woocommerce_payment_tokenmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.681038Z 0 [Warning] InnoDB: Ignoring tablespace `client_hcwong/wp_woocommerce_payment_tokenmeta` because it could not be opened.
2025-06-10T12:22:24.681668Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.682165Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.682510Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.682880Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_hcwong\wp_woocommerce_payment_tokens.ibd' OS error: 103
2025-06-10T12:22:24.683560Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.683857Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.684307Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_hcwong/wp_woocommerce_payment_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.684893Z 0 [Warning] InnoDB: Ignoring tablespace `client_hcwong/wp_woocommerce_payment_tokens` because it could not be opened.
2025-06-10T12:22:24.685418Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.685677Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.685936Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.686365Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_hcwong\wp_woocommerce_sessions.ibd' OS error: 103
2025-06-10T12:22:24.686700Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.686947Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.687452Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_hcwong/wp_woocommerce_sessions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.688039Z 0 [Warning] InnoDB: Ignoring tablespace `client_hcwong/wp_woocommerce_sessions` because it could not be opened.
2025-06-10T12:22:24.688595Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.688848Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.689148Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.689564Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_hcwong\wp_woocommerce_shipping_zone_locations.ibd' OS error: 103
2025-06-10T12:22:24.689951Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.690273Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.690691Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_hcwong/wp_woocommerce_shipping_zone_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.691379Z 0 [Warning] InnoDB: Ignoring tablespace `client_hcwong/wp_woocommerce_shipping_zone_locations` because it could not be opened.
2025-06-10T12:22:24.691827Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.692133Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.692455Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.692861Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_hcwong\wp_woocommerce_shipping_zone_methods.ibd' OS error: 103
2025-06-10T12:22:24.693266Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.693560Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.693966Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_hcwong/wp_woocommerce_shipping_zone_methods`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.694647Z 0 [Warning] InnoDB: Ignoring tablespace `client_hcwong/wp_woocommerce_shipping_zone_methods` because it could not be opened.
2025-06-10T12:22:24.695113Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.695397Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.695658Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.696180Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_hcwong\wp_woocommerce_shipping_zones.ibd' OS error: 103
2025-06-10T12:22:24.697023Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.697287Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.698247Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_hcwong/wp_woocommerce_shipping_zones`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.698953Z 0 [Warning] InnoDB: Ignoring tablespace `client_hcwong/wp_woocommerce_shipping_zones` because it could not be opened.
2025-06-10T12:22:24.699450Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.699758Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.700033Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.700541Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_hcwong\wp_woocommerce_tax_rate_locations.ibd' OS error: 103
2025-06-10T12:22:24.701227Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.701792Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.702301Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_hcwong/wp_woocommerce_tax_rate_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.703065Z 0 [Warning] InnoDB: Ignoring tablespace `client_hcwong/wp_woocommerce_tax_rate_locations` because it could not be opened.
2025-06-10T12:22:24.703703Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.704055Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.704374Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.704907Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_hcwong\wp_woocommerce_tax_rates.ibd' OS error: 103
2025-06-10T12:22:24.705374Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.705952Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.706721Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_hcwong/wp_woocommerce_tax_rates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.707527Z 0 [Warning] InnoDB: Ignoring tablespace `client_hcwong/wp_woocommerce_tax_rates` because it could not be opened.
2025-06-10T12:22:24.708090Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.708387Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.708728Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.709238Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_hcwong\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:24.709747Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.710236Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.710808Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_hcwong/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.711658Z 0 [Warning] InnoDB: Ignoring tablespace `client_hcwong/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:24.712175Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.712522Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.712859Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.713353Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_hcwong\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:24.713821Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.714111Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.714549Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_hcwong/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.715280Z 0 [Warning] InnoDB: Ignoring tablespace `client_hcwong/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:24.715984Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.716312Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.716713Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.717124Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_hcwong\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:24.717475Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.717844Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.718363Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_hcwong/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.719118Z 0 [Warning] InnoDB: Ignoring tablespace `client_hcwong/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:24.719621Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.719930Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.720212Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.720735Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_hcwong\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:24.721106Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.721375Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.721933Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_hcwong/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.722580Z 0 [Warning] InnoDB: Ignoring tablespace `client_hcwong/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:24.723104Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.723376Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.724165Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.724670Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms\actions.ibd' OS error: 103
2025-06-10T12:22:24.725152Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.725445Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.725956Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms/actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.726695Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms/actions` because it could not be opened.
2025-06-10T12:22:24.727686Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.728043Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.728334Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.728797Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms\ci_sessions.ibd' OS error: 103
2025-06-10T12:22:24.729126Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.729396Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.729890Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms/ci_sessions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.730647Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms/ci_sessions` because it could not be opened.
2025-06-10T12:22:24.731192Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.731494Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.731799Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.732189Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms\contracts.ibd' OS error: 103
2025-06-10T12:22:24.732520Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.732811Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.733232Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms/contracts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.733819Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms/contracts` because it could not be opened.
2025-06-10T12:22:24.734204Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.734470Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.734796Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.735184Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms\dayoffs.ibd' OS error: 103
2025-06-10T12:22:24.735496Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.735791Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.736209Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms/dayoffs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.736791Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms/dayoffs` because it could not be opened.
2025-06-10T12:22:24.737147Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.737413Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.737751Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.738138Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms\delegations.ibd' OS error: 103
2025-06-10T12:22:24.738462Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.738780Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.739200Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms/delegations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.739806Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms/delegations` because it could not be opened.
2025-06-10T12:22:24.740200Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.740470Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.740777Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.741165Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms\entitleddays.ibd' OS error: 103
2025-06-10T12:22:24.741498Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.741800Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.742216Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms/entitleddays`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.742806Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms/entitleddays` because it could not be opened.
2025-06-10T12:22:24.743477Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.744341Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.745529Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.746101Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms\excluded_types.ibd' OS error: 103
2025-06-10T12:22:24.746521Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.746891Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.747444Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms/excluded_types`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.748213Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms/excluded_types` because it could not be opened.
2025-06-10T12:22:24.748680Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.748936Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.749411Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.749796Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms\leaves.ibd' OS error: 103
2025-06-10T12:22:24.750215Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.750487Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.750932Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms/leaves`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.751724Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms/leaves` because it could not be opened.
2025-06-10T12:22:24.752175Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.752443Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.752718Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.753236Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms\leaves_history.ibd' OS error: 103
2025-06-10T12:22:24.753646Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.753962Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.754451Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms/leaves_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.755071Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms/leaves_history` because it could not be opened.
2025-06-10T12:22:24.755499Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.755770Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.756076Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.756469Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms\oauth_access_tokens.ibd' OS error: 103
2025-06-10T12:22:24.756809Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.757149Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.757664Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms/oauth_access_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.758320Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms/oauth_access_tokens` because it could not be opened.
2025-06-10T12:22:24.758772Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.759282Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.759613Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.760064Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms\oauth_applications.ibd' OS error: 103
2025-06-10T12:22:24.760385Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.760633Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.761099Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms/oauth_applications`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.761692Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms/oauth_applications` because it could not be opened.
2025-06-10T12:22:24.762176Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.762433Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.762694Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.763148Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms\oauth_authorization_codes.ibd' OS error: 103
2025-06-10T12:22:24.763504Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.763797Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.764283Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms/oauth_authorization_codes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.764901Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms/oauth_authorization_codes` because it could not be opened.
2025-06-10T12:22:24.765452Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.765789Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.766114Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.766519Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms\oauth_clients.ibd' OS error: 103
2025-06-10T12:22:24.766857Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.767306Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.767738Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms/oauth_clients`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.768355Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms/oauth_clients` because it could not be opened.
2025-06-10T12:22:24.768771Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.769083Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.769359Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.769806Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms\oauth_jwt.ibd' OS error: 103
2025-06-10T12:22:24.770336Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.770627Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.771124Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms/oauth_jwt`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.771804Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms/oauth_jwt` because it could not be opened.
2025-06-10T12:22:24.772319Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.772602Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.772885Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.773325Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms\oauth_refresh_tokens.ibd' OS error: 103
2025-06-10T12:22:24.773669Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.773967Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.774423Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms/oauth_refresh_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.775055Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms/oauth_refresh_tokens` because it could not be opened.
2025-06-10T12:22:24.775716Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.776102Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.776457Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.777660Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms\oauth_scopes.ibd' OS error: 103
2025-06-10T12:22:24.778223Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.778497Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.778997Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms/oauth_scopes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.779667Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms/oauth_scopes` because it could not be opened.
2025-06-10T12:22:24.780162Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.780629Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.780998Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.781392Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms\oauth_users.ibd' OS error: 103
2025-06-10T12:22:24.781858Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.782257Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.782736Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms/oauth_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.783406Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms/oauth_users` because it could not be opened.
2025-06-10T12:22:24.783898Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.784248Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.784527Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.784969Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms\org_lists.ibd' OS error: 103
2025-06-10T12:22:24.785302Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.785569Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.786068Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms/org_lists`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.786692Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms/org_lists` because it could not be opened.
2025-06-10T12:22:24.787202Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.787518Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.787790Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.788219Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms\org_lists_employees.ibd' OS error: 103
2025-06-10T12:22:24.788555Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.788840Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.789318Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms/org_lists_employees`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.789969Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms/org_lists_employees` because it could not be opened.
2025-06-10T12:22:24.790383Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.790647Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.790993Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.791479Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms\organization.ibd' OS error: 103
2025-06-10T12:22:24.791803Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.792133Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.792548Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms/organization`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.793172Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms/organization` because it could not be opened.
2025-06-10T12:22:24.793544Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.793809Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.794146Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.794526Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms\overtime.ibd' OS error: 103
2025-06-10T12:22:24.794860Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.795245Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.795677Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms/overtime`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.796307Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms/overtime` because it could not be opened.
2025-06-10T12:22:24.796863Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.797211Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.797479Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.797865Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms\parameters.ibd' OS error: 103
2025-06-10T12:22:24.798253Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.798515Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.798997Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms/parameters`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.799519Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms/parameters` because it could not be opened.
2025-06-10T12:22:24.799932Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.800226Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.800496Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.800941Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms\positions.ibd' OS error: 103
2025-06-10T12:22:24.801389Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.801652Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.802124Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms/positions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.802686Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms/positions` because it could not be opened.
2025-06-10T12:22:24.803179Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.803465Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.803724Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.804188Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms\roles.ibd' OS error: 103
2025-06-10T12:22:24.804478Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.804727Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.805253Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms/roles`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.805802Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms/roles` because it could not be opened.
2025-06-10T12:22:24.806266Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.806520Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.806776Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.807245Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms\status.ibd' OS error: 103
2025-06-10T12:22:24.807732Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.808117Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.809055Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms/status`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.810302Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms/status` because it could not be opened.
2025-06-10T12:22:24.810932Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.811335Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.811713Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.812131Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms\types.ibd' OS error: 103
2025-06-10T12:22:24.812473Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.812738Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.813150Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms/types`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.813729Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms/types` because it could not be opened.
2025-06-10T12:22:24.814110Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.814463Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.814739Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.815126Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms\users.ibd' OS error: 103
2025-06-10T12:22:24.815570Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.815898Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.816435Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms/users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.817026Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms/users` because it could not be opened.
2025-06-10T12:22:24.817486Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.818019Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.818364Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.818900Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms2\actions.ibd' OS error: 103
2025-06-10T12:22:24.819258Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.819575Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.820102Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms2/actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.820884Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms2/actions` because it could not be opened.
2025-06-10T12:22:24.821417Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.821777Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.822075Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.822485Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms2\ci_sessions.ibd' OS error: 103
2025-06-10T12:22:24.822805Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.823067Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.823635Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms2/ci_sessions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.824201Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms2/ci_sessions` because it could not be opened.
2025-06-10T12:22:24.824715Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.825030Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.825342Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.825731Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms2\contracts.ibd' OS error: 103
2025-06-10T12:22:24.826054Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.826388Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.826806Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms2/contracts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.827385Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms2/contracts` because it could not be opened.
2025-06-10T12:22:24.827790Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.828052Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.828356Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.828876Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms2\dayoffs.ibd' OS error: 103
2025-06-10T12:22:24.829313Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.829659Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.830120Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms2/dayoffs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.830801Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms2/dayoffs` because it could not be opened.
2025-06-10T12:22:24.831351Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.831618Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.831909Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.832346Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms2\delegations.ibd' OS error: 103
2025-06-10T12:22:24.832651Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.832901Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.833381Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms2/delegations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.833922Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms2/delegations` because it could not be opened.
2025-06-10T12:22:24.834424Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.834796Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.835204Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.835678Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms2\entitleddays.ibd' OS error: 103
2025-06-10T12:22:24.835984Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.836314Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.836718Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms2/entitleddays`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.837436Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms2/entitleddays` because it could not be opened.
2025-06-10T12:22:24.838208Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.838545Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.839044Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.839503Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms2\excluded_types.ibd' OS error: 103
2025-06-10T12:22:24.839810Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.840058Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.840698Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms2/excluded_types`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.842331Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms2/excluded_types` because it could not be opened.
2025-06-10T12:22:24.843312Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.843792Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.844182Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.844587Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms2\leaves.ibd' OS error: 103
2025-06-10T12:22:24.844924Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.845557Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.845991Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms2/leaves`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.846616Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms2/leaves` because it could not be opened.
2025-06-10T12:22:24.847337Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.847630Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.847895Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.848455Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms2\leaves_history.ibd' OS error: 103
2025-06-10T12:22:24.848835Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.849289Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.849828Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms2/leaves_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.850523Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms2/leaves_history` because it could not be opened.
2025-06-10T12:22:24.851389Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.851939Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.852450Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.853167Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms2\oauth_access_tokens.ibd' OS error: 103
2025-06-10T12:22:24.853517Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.853764Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.854272Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms2/oauth_access_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.854849Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms2/oauth_access_tokens` because it could not be opened.
2025-06-10T12:22:24.855383Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.855690Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.855997Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.856533Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms2\oauth_applications.ibd' OS error: 103
2025-06-10T12:22:24.856893Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.857275Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.857784Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms2/oauth_applications`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.858589Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms2/oauth_applications` because it could not be opened.
2025-06-10T12:22:24.859182Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.859447Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.859706Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.860139Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms2\oauth_authorization_codes.ibd' OS error: 103
2025-06-10T12:22:24.860488Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.860735Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.861232Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms2/oauth_authorization_codes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.861971Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms2/oauth_authorization_codes` because it could not be opened.
2025-06-10T12:22:24.862448Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.862704Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.862962Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.863498Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms2\oauth_clients.ibd' OS error: 103
2025-06-10T12:22:24.863805Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.864091Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.864507Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms2/oauth_clients`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.865140Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms2/oauth_clients` because it could not be opened.
2025-06-10T12:22:24.865798Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.866283Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.867124Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.867643Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms2\oauth_jwt.ibd' OS error: 103
2025-06-10T12:22:24.868079Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.868398Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.868877Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms2/oauth_jwt`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.869639Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms2/oauth_jwt` because it could not be opened.
2025-06-10T12:22:24.870129Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.870465Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.870802Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.871314Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms2\oauth_refresh_tokens.ibd' OS error: 103
2025-06-10T12:22:24.871662Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.871928Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.872732Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms2/oauth_refresh_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.873468Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms2/oauth_refresh_tokens` because it could not be opened.
2025-06-10T12:22:24.874325Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.875148Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.875422Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.876004Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms2\oauth_scopes.ibd' OS error: 103
2025-06-10T12:22:24.876655Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.877145Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.877773Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms2/oauth_scopes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.878562Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms2/oauth_scopes` because it could not be opened.
2025-06-10T12:22:24.879035Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.879323Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.879609Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.879979Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms2\oauth_users.ibd' OS error: 103
2025-06-10T12:22:24.880299Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.880637Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.881046Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms2/oauth_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.881823Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms2/oauth_users` because it could not be opened.
2025-06-10T12:22:24.882758Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.883218Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.883743Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.884125Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms2\org_lists.ibd' OS error: 103
2025-06-10T12:22:24.884509Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.884772Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.885250Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms2/org_lists`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.886001Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms2/org_lists` because it could not be opened.
2025-06-10T12:22:24.886564Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.886850Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.887124Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.887547Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms2\org_lists_employees.ibd' OS error: 103
2025-06-10T12:22:24.887902Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.888178Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.888807Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms2/org_lists_employees`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.889492Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms2/org_lists_employees` because it could not be opened.
2025-06-10T12:22:24.889910Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.890167Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.890531Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.890966Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms2\organization.ibd' OS error: 103
2025-06-10T12:22:24.891341Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.891611Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.892037Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms2/organization`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.892658Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms2/organization` because it could not be opened.
2025-06-10T12:22:24.893207Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.893565Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.893829Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.894366Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms2\overtime.ibd' OS error: 103
2025-06-10T12:22:24.894759Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.895013Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.895534Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms2/overtime`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.896121Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms2/overtime` because it could not be opened.
2025-06-10T12:22:24.896668Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.897046Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.897602Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.898006Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms2\parameters.ibd' OS error: 103
2025-06-10T12:22:24.898378Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.898650Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.899060Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms2/parameters`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.899704Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms2/parameters` because it could not be opened.
2025-06-10T12:22:24.900496Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.900982Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.901304Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.901888Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms2\positions.ibd' OS error: 103
2025-06-10T12:22:24.902200Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.902625Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.903111Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms2/positions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.904321Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms2/positions` because it could not be opened.
2025-06-10T12:22:24.905016Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.905723Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.906018Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.906660Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms2\roles.ibd' OS error: 103
2025-06-10T12:22:24.907288Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.907611Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.908036Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms2/roles`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.908627Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms2/roles` because it could not be opened.
2025-06-10T12:22:24.909072Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.909352Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.909626Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.910086Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms2\status.ibd' OS error: 103
2025-06-10T12:22:24.910457Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.910733Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.911302Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms2/status`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.911882Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms2/status` because it could not be opened.
2025-06-10T12:22:24.912368Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.912647Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.912984Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.913437Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms2\types.ibd' OS error: 103
2025-06-10T12:22:24.913761Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.914045Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.914588Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms2/types`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.915291Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms2/types` because it could not be opened.
2025-06-10T12:22:24.915682Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.916002Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.916346Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.916750Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_lms2\users.ibd' OS error: 103
2025-06-10T12:22:24.917100Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.917372Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.917797Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_lms2/users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.918433Z 0 [Warning] InnoDB: Ignoring tablespace `client_lms2/users` because it could not be opened.
2025-06-10T12:22:24.919073Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.919395Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.919739Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.920200Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi1\wp_ahm_asset_links.ibd' OS error: 103
2025-06-10T12:22:24.920585Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.920844Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.921380Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi1/wp_ahm_asset_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.921924Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi1/wp_ahm_asset_links` because it could not be opened.
2025-06-10T12:22:24.922528Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.922806Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.923175Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.923571Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi1\wp_ahm_assets.ibd' OS error: 103
2025-06-10T12:22:24.923908Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.924243Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.924641Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi1/wp_ahm_assets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.925334Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi1/wp_ahm_assets` because it could not be opened.
2025-06-10T12:22:24.925846Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.926163Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.926503Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.926941Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi1\wp_ahm_download_stats.ibd' OS error: 103
2025-06-10T12:22:24.927367Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.927627Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.928101Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi1/wp_ahm_download_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.928686Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi1/wp_ahm_download_stats` because it could not be opened.
2025-06-10T12:22:24.929161Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.929429Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.929702Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.930183Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi1\wp_ahm_emails.ibd' OS error: 103
2025-06-10T12:22:24.930677Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.931127Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.931838Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi1/wp_ahm_emails`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.932519Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi1/wp_ahm_emails` because it could not be opened.
2025-06-10T12:22:24.933103Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.933464Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.933798Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.934287Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi1\wp_ahm_sessions.ibd' OS error: 103
2025-06-10T12:22:24.934620Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.934884Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.935401Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi1/wp_ahm_sessions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.935964Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi1/wp_ahm_sessions` because it could not be opened.
2025-06-10T12:22:24.936486Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.937153Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.938384Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.939062Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi1\wp_ahm_social_conns.ibd' OS error: 103
2025-06-10T12:22:24.939871Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.940199Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.940649Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi1/wp_ahm_social_conns`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.941318Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi1/wp_ahm_social_conns` because it could not be opened.
2025-06-10T12:22:24.941759Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.942083Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.942362Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.942748Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi1\wp_apmm_custom_theme.ibd' OS error: 103
2025-06-10T12:22:24.943138Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.943402Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.943820Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi1/wp_apmm_custom_theme`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.944464Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi1/wp_apmm_custom_theme` because it could not be opened.
2025-06-10T12:22:24.944902Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.945234Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.945510Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.945987Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi1\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:24.946363Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.946655Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.947154Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi1/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.947772Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi1/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:24.948252Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.948518Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.948788Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.949229Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi1\wp_comments.ibd' OS error: 103
2025-06-10T12:22:24.949553Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.949815Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.950307Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi1/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.950886Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi1/wp_comments` because it could not be opened.
2025-06-10T12:22:24.951362Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.951631Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.951956Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.952434Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi1\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:24.952767Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.953065Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.953492Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi1/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.954070Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi1/wp_fbv` because it could not be opened.
2025-06-10T12:22:24.954458Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.954779Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.955100Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.955495Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi1\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:24.955846Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.956177Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.956588Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi1/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.957236Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi1/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:24.957623Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.957953Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.958271Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.958665Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi1\wp_links.ibd' OS error: 103
2025-06-10T12:22:24.959011Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.959289Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.959701Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi1/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.960283Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi1/wp_links` because it could not be opened.
2025-06-10T12:22:24.960641Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.960898Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.961249Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.961682Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi1\wp_msw_stocks.ibd' OS error: 103
2025-06-10T12:22:24.962032Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.962299Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.962712Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi1/wp_msw_stocks`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.963309Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi1/wp_msw_stocks` because it could not be opened.
2025-06-10T12:22:24.963710Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.964000Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.964426Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.964880Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi1\wp_newsletter.ibd' OS error: 103
2025-06-10T12:22:24.965325Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.965598Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.966053Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi1/wp_newsletter`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.966636Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi1/wp_newsletter` because it could not be opened.
2025-06-10T12:22:24.967132Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.967413Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.967730Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.968124Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi1\wp_newsletter_emails.ibd' OS error: 103
2025-06-10T12:22:24.969169Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.969857Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.970318Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi1/wp_newsletter_emails`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.971000Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi1/wp_newsletter_emails` because it could not be opened.
2025-06-10T12:22:24.971445Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.971741Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.972049Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.972463Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi1\wp_newsletter_sent.ibd' OS error: 103
2025-06-10T12:22:24.972806Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.973061Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.973563Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi1/wp_newsletter_sent`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.974156Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi1/wp_newsletter_sent` because it could not be opened.
2025-06-10T12:22:24.974728Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.975012Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.975276Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.975762Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi1\wp_newsletter_stats.ibd' OS error: 103
2025-06-10T12:22:24.976110Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.976378Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.976883Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi1/wp_newsletter_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.977569Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi1/wp_newsletter_stats` because it could not be opened.
2025-06-10T12:22:24.978003Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.978271Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.978708Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.979106Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi1\wp_newsletter_user_logs.ibd' OS error: 103
2025-06-10T12:22:24.979470Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.979731Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.980138Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi1/wp_newsletter_user_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.980800Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi1/wp_newsletter_user_logs` because it could not be opened.
2025-06-10T12:22:24.981299Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.981585Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.981859Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.982242Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi1\wp_options.ibd' OS error: 103
2025-06-10T12:22:24.982605Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.982875Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.983294Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi1/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.983887Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi1/wp_options` because it could not be opened.
2025-06-10T12:22:24.984273Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.984884Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.985188Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.985665Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi1\wp_post_views.ibd' OS error: 103
2025-06-10T12:22:24.985982Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.986237Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.986803Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi1/wp_post_views`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.987345Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi1/wp_post_views` because it could not be opened.
2025-06-10T12:22:24.987813Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.988068Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.988328Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.988795Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi1\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:24.989097Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.989345Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.989806Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi1/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.990334Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi1/wp_postmeta` because it could not be opened.
2025-06-10T12:22:24.990874Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.991150Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.991485Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.991847Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi1\wp_posts.ibd' OS error: 103
2025-06-10T12:22:24.992148Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.992498Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.992896Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi1/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.993519Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi1/wp_posts` because it could not be opened.
2025-06-10T12:22:24.993863Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.994117Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.994433Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.994814Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi1\wp_revslider_css.ibd' OS error: 103
2025-06-10T12:22:24.995127Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.995467Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.996117Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi1/wp_revslider_css`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.996737Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi1/wp_revslider_css` because it could not be opened.
2025-06-10T12:22:24.997223Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:24.997570Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:24.997929Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:24.998297Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi1\wp_revslider_css_bkp.ibd' OS error: 103
2025-06-10T12:22:24.998690Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:24.998939Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:24.999339Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi1/wp_revslider_css_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:24.999941Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi1/wp_revslider_css_bkp` because it could not be opened.
2025-06-10T12:22:25.000310Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.000663Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.000922Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.001288Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi1\wp_revslider_layer_animations.ibd' OS error: 103
2025-06-10T12:22:25.001737Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.002120Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.002579Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi1/wp_revslider_layer_animations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.003262Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi1/wp_revslider_layer_animations` because it could not be opened.
2025-06-10T12:22:25.003784Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.004040Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.004302Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.004855Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi1\wp_revslider_layer_animations_bkp.ibd' OS error: 103
2025-06-10T12:22:25.005272Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.005582Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.005985Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi1/wp_revslider_layer_animations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.006649Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi1/wp_revslider_layer_animations_bkp` because it could not be opened.
2025-06-10T12:22:25.007055Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.007380Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.007665Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.008030Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi1\wp_revslider_navigations.ibd' OS error: 103
2025-06-10T12:22:25.008468Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.008877Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.009310Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi1/wp_revslider_navigations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.009952Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi1/wp_revslider_navigations` because it could not be opened.
2025-06-10T12:22:25.010386Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.010796Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.011069Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.011489Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi1\wp_revslider_navigations_bkp.ibd' OS error: 103
2025-06-10T12:22:25.011836Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.012089Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.012553Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi1/wp_revslider_navigations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.013204Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi1/wp_revslider_navigations_bkp` because it could not be opened.
2025-06-10T12:22:25.013721Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.014008Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.014268Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.014937Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi1\wp_revslider_sliders.ibd' OS error: 103
2025-06-10T12:22:25.015346Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.015625Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.016048Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi1/wp_revslider_sliders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.016990Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi1/wp_revslider_sliders` because it could not be opened.
2025-06-10T12:22:25.017448Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.017725Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.018082Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.018468Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi1\wp_revslider_sliders_bkp.ibd' OS error: 103
2025-06-10T12:22:25.019231Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.019501Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.019960Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi1/wp_revslider_sliders_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.020743Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi1/wp_revslider_sliders_bkp` because it could not be opened.
2025-06-10T12:22:25.021312Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.021718Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.022014Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.022682Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi1\wp_revslider_slides.ibd' OS error: 103
2025-06-10T12:22:25.023137Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.023495Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.023922Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi1/wp_revslider_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.024604Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi1/wp_revslider_slides` because it could not be opened.
2025-06-10T12:22:25.025254Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.025551Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.025969Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.026507Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi1\wp_revslider_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:25.026876Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.027187Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.027706Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi1/wp_revslider_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.028355Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi1/wp_revslider_slides_bkp` because it could not be opened.
2025-06-10T12:22:25.028782Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.029083Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.029484Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.029875Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi1\wp_revslider_static_slides.ibd' OS error: 103
2025-06-10T12:22:25.030425Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.030743Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.031220Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi1/wp_revslider_static_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.031827Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi1/wp_revslider_static_slides` because it could not be opened.
2025-06-10T12:22:25.032329Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.032618Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.032896Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.033312Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi1\wp_revslider_static_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:25.033683Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.033991Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.034442Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi1/wp_revslider_static_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.035043Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi1/wp_revslider_static_slides_bkp` because it could not be opened.
2025-06-10T12:22:25.035506Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.035773Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.036047Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.036487Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi1\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:25.036864Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.037151Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.037559Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi1/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.038163Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi1/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:25.038548Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.038802Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.039070Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.039485Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi1\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:25.039801Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.040049Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.040617Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi1/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.041247Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi1/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:25.041614Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.041868Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.042177Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.042595Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi1\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:25.042951Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.043280Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.043756Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi1/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.044384Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi1/wp_termmeta` because it could not be opened.
2025-06-10T12:22:25.044797Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.045180Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.045644Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.046034Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi1\wp_terms.ibd' OS error: 103
2025-06-10T12:22:25.046420Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.046671Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.047134Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi1/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.047679Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi1/wp_terms` because it could not be opened.
2025-06-10T12:22:25.049082Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.050382Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.051004Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.051401Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi1\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:25.052094Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.052353Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.052748Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi1/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.053352Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi1/wp_usermeta` because it could not be opened.
2025-06-10T12:22:25.053953Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.054227Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.054491Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.054902Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi1\wp_users.ibd' OS error: 103
2025-06-10T12:22:25.055231Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.055485Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.055954Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi1/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.056617Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi1/wp_users` because it could not be opened.
2025-06-10T12:22:25.057158Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.057424Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.058006Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.058466Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi1\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:25.058896Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.059169Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.059581Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi1/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.060250Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi1/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:25.060675Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.061047Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.061438Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.061808Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi1\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:25.062232Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.062484Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.062957Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi1/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.063511Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi1/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:25.063954Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.064313Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.064572Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.064999Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi1\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:25.065310Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.065606Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.066102Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi1/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.066638Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi1/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:25.067146Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.067468Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.067767Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.068252Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi1\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:25.068788Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.069130Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.069545Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi1/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.070202Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi1/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:25.070619Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.070967Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.071236Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.071595Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi10\wp_ahm_asset_links.ibd' OS error: 103
2025-06-10T12:22:25.072037Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.072299Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.072693Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi10/wp_ahm_asset_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.073334Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi10/wp_ahm_asset_links` because it could not be opened.
2025-06-10T12:22:25.073702Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.074077Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.074331Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.074689Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi10\wp_ahm_assets.ibd' OS error: 103
2025-06-10T12:22:25.075099Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.075349Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.075736Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi10/wp_ahm_assets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.076561Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi10/wp_ahm_assets` because it could not be opened.
2025-06-10T12:22:25.077093Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.077361Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.077633Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.078063Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi10\wp_ahm_download_stats.ibd' OS error: 103
2025-06-10T12:22:25.078405Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.078667Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.079123Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi10/wp_ahm_download_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.080042Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi10/wp_ahm_download_stats` because it could not be opened.
2025-06-10T12:22:25.081994Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.082356Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.082688Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.083076Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi10\wp_ahm_emails.ibd' OS error: 103
2025-06-10T12:22:25.083437Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.083722Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.084178Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi10/wp_ahm_emails`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.084767Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi10/wp_ahm_emails` because it could not be opened.
2025-06-10T12:22:25.085229Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.085503Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.085777Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.086211Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi10\wp_ahm_sessions.ibd' OS error: 103
2025-06-10T12:22:25.086540Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.086802Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.087302Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi10/wp_ahm_sessions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.088017Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi10/wp_ahm_sessions` because it could not be opened.
2025-06-10T12:22:25.088563Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.088835Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.089123Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.089557Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi10\wp_ahm_social_conns.ibd' OS error: 103
2025-06-10T12:22:25.089966Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.090301Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.090762Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi10/wp_ahm_social_conns`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.091433Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi10/wp_ahm_social_conns` because it could not be opened.
2025-06-10T12:22:25.091850Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.092133Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.092432Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.092793Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi10\wp_cf7_vdata.ibd' OS error: 103
2025-06-10T12:22:25.093140Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.093451Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.093880Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi10/wp_cf7_vdata`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.094468Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi10/wp_cf7_vdata` because it could not be opened.
2025-06-10T12:22:25.094830Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.095084Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.095418Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.095792Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi10\wp_cf7_vdata_entry.ibd' OS error: 103
2025-06-10T12:22:25.096169Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.096442Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.096835Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi10/wp_cf7_vdata_entry`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.097481Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi10/wp_cf7_vdata_entry` because it could not be opened.
2025-06-10T12:22:25.097845Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.098114Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.098458Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.098852Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi10\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:25.099242Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.099504Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.099899Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi10/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.100590Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi10/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:25.100950Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.101275Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.101534Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.101894Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi10\wp_comments.ibd' OS error: 103
2025-06-10T12:22:25.102303Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.102554Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.103163Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi10/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.103745Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi10/wp_comments` because it could not be opened.
2025-06-10T12:22:25.104188Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.104461Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.104787Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.105228Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi10\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:25.105556Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.105829Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.106281Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi10/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.106850Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi10/wp_fbv` because it could not be opened.
2025-06-10T12:22:25.107278Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.107558Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.107835Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.108279Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi10\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:25.108652Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.109169Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.109743Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi10/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.110391Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi10/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:25.110817Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.111113Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.111446Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.111832Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi10\wp_links.ibd' OS error: 103
2025-06-10T12:22:25.112652Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.112900Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.113382Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi10/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.113973Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi10/wp_links` because it could not be opened.
2025-06-10T12:22:25.114719Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.114999Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.115273Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.115670Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi10\wp_msw_stocks.ibd' OS error: 103
2025-06-10T12:22:25.116045Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.116311Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.116766Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi10/wp_msw_stocks`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.117337Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi10/wp_msw_stocks` because it could not be opened.
2025-06-10T12:22:25.117793Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.118065Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.118338Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.118770Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi10\wp_newsletter.ibd' OS error: 103
2025-06-10T12:22:25.119125Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.119395Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.119854Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi10/wp_newsletter`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.120422Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi10/wp_newsletter` because it could not be opened.
2025-06-10T12:22:25.120930Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.121226Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.121507Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.121971Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi10\wp_newsletter_emails.ibd' OS error: 103
2025-06-10T12:22:25.122334Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.122601Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.123049Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi10/wp_newsletter_emails`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.123630Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi10/wp_newsletter_emails` because it could not be opened.
2025-06-10T12:22:25.124082Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.124350Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.124622Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.125037Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi10\wp_newsletter_sent.ibd' OS error: 103
2025-06-10T12:22:25.125376Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.125652Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.126085Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi10/wp_newsletter_sent`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.126674Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi10/wp_newsletter_sent` because it could not be opened.
2025-06-10T12:22:25.127080Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.127341Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.127613Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.128166Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi10\wp_newsletter_stats.ibd' OS error: 103
2025-06-10T12:22:25.128526Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.128857Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.129249Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi10/wp_newsletter_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.129909Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi10/wp_newsletter_stats` because it could not be opened.
2025-06-10T12:22:25.130321Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.130574Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.130894Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.131255Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi10\wp_newsletter_user_logs.ibd' OS error: 103
2025-06-10T12:22:25.131784Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.132107Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.132504Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi10/wp_newsletter_user_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.133166Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi10/wp_newsletter_user_logs` because it could not be opened.
2025-06-10T12:22:25.133550Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.133869Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.134129Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.134645Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi10\wp_options.ibd' OS error: 103
2025-06-10T12:22:25.134998Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.135267Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.135712Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi10/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.136271Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi10/wp_options` because it could not be opened.
2025-06-10T12:22:25.136672Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.136940Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.137212Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.137590Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi10\wp_post_views.ibd' OS error: 103
2025-06-10T12:22:25.137945Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.138207Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.138638Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi10/wp_post_views`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.139234Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi10/wp_post_views` because it could not be opened.
2025-06-10T12:22:25.139669Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.139948Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.140221Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.140844Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi10\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:25.141197Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.141459Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.141985Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi10/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.142502Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi10/wp_postmeta` because it could not be opened.
2025-06-10T12:22:25.143013Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.143260Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.143569Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.144104Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi10\wp_posts.ibd' OS error: 103
2025-06-10T12:22:25.144909Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.145155Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.146119Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi10/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.146819Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi10/wp_posts` because it could not be opened.
2025-06-10T12:22:25.147262Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.147562Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.147828Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.148228Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi10\wp_redirection_404.ibd' OS error: 103
2025-06-10T12:22:25.148581Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.148841Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.149257Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi10/wp_redirection_404`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.149859Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi10/wp_redirection_404` because it could not be opened.
2025-06-10T12:22:25.150296Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.150615Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.150892Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.151279Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi10\wp_redirection_groups.ibd' OS error: 103
2025-06-10T12:22:25.151664Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.151927Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.152380Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi10/wp_redirection_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.152995Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi10/wp_redirection_groups` because it could not be opened.
2025-06-10T12:22:25.153507Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.153786Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.154108Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.154516Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi10\wp_redirection_items.ibd' OS error: 103
2025-06-10T12:22:25.154859Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.155116Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.155559Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi10/wp_redirection_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.156149Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi10/wp_redirection_items` because it could not be opened.
2025-06-10T12:22:25.156598Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.156850Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.157108Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.157561Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi10\wp_redirection_logs.ibd' OS error: 103
2025-06-10T12:22:25.157881Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.158128Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.158575Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi10/wp_redirection_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.159118Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi10/wp_redirection_logs` because it could not be opened.
2025-06-10T12:22:25.159604Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.159855Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.160112Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.160535Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi10\wp_revslider_css.ibd' OS error: 103
2025-06-10T12:22:25.160929Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.161194Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.161616Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi10/wp_revslider_css`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.162176Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi10/wp_revslider_css` because it could not be opened.
2025-06-10T12:22:25.162621Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.162891Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.163152Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.163600Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi10\wp_revslider_css_bkp.ibd' OS error: 103
2025-06-10T12:22:25.163927Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.164181Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.164660Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi10/wp_revslider_css_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.165218Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi10/wp_revslider_css_bkp` because it could not be opened.
2025-06-10T12:22:25.165738Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.165995Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.166254Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.166683Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi10\wp_revslider_layer_animations.ibd' OS error: 103
2025-06-10T12:22:25.167092Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.167412Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.167818Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi10/wp_revslider_layer_animations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.168465Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi10/wp_revslider_layer_animations` because it could not be opened.
2025-06-10T12:22:25.168854Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.169107Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.169433Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.169820Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi10\wp_revslider_layer_animations_bkp.ibd' OS error: 103
2025-06-10T12:22:25.170190Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.170627Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.171082Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi10/wp_revslider_layer_animations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.171783Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi10/wp_revslider_layer_animations_bkp` because it could not be opened.
2025-06-10T12:22:25.172380Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.172680Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.172993Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.173483Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi10\wp_revslider_navigations.ibd' OS error: 103
2025-06-10T12:22:25.173855Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.174098Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.174646Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi10/wp_revslider_navigations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.175402Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi10/wp_revslider_navigations` because it could not be opened.
2025-06-10T12:22:25.175944Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.176216Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.176528Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.176899Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi10\wp_revslider_navigations_bkp.ibd' OS error: 103
2025-06-10T12:22:25.177351Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.177745Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.178315Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi10/wp_revslider_navigations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.178940Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi10/wp_revslider_navigations_bkp` because it could not be opened.
2025-06-10T12:22:25.179444Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.179699Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.179955Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.180551Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi10\wp_revslider_sliders.ibd' OS error: 103
2025-06-10T12:22:25.180910Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.181242Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.181669Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi10/wp_revslider_sliders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.182331Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi10/wp_revslider_sliders` because it could not be opened.
2025-06-10T12:22:25.182790Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.183146Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.183520Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.183890Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi10\wp_revslider_sliders_bkp.ibd' OS error: 103
2025-06-10T12:22:25.184326Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.184590Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.185079Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi10/wp_revslider_sliders_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.185802Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi10/wp_revslider_sliders_bkp` because it could not be opened.
2025-06-10T12:22:25.186429Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.186706Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.187434Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.187821Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi10\wp_revslider_slides.ibd' OS error: 103
2025-06-10T12:22:25.188362Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.188706Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.189221Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi10/wp_revslider_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.189912Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi10/wp_revslider_slides` because it could not be opened.
2025-06-10T12:22:25.190467Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.190721Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.191060Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.191454Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi10\wp_revslider_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:25.191786Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.192149Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.192555Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi10/wp_revslider_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.193218Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi10/wp_revslider_slides_bkp` because it could not be opened.
2025-06-10T12:22:25.193780Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.194123Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.194388Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.194902Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi10\wp_revslider_static_slides.ibd' OS error: 103
2025-06-10T12:22:25.195321Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.195572Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.196001Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi10/wp_revslider_static_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.196629Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi10/wp_revslider_static_slides` because it could not be opened.
2025-06-10T12:22:25.197071Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.197338Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.197593Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.197994Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi10\wp_revslider_static_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:25.198364Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.198625Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.199068Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi10/wp_revslider_static_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.199736Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi10/wp_revslider_static_slides_bkp` because it could not be opened.
2025-06-10T12:22:25.200365Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.200712Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.201045Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.201459Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi10\wp_sbi_instagram_feeds_posts.ibd' OS error: 103
2025-06-10T12:22:25.201802Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.202132Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.202557Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi10/wp_sbi_instagram_feeds_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.203246Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi10/wp_sbi_instagram_feeds_posts` because it could not be opened.
2025-06-10T12:22:25.203769Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.204124Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.204392Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.204768Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi10\wp_sbi_instagram_posts.ibd' OS error: 103
2025-06-10T12:22:25.205235Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.205541Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.206084Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi10/wp_sbi_instagram_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.206756Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi10/wp_sbi_instagram_posts` because it could not be opened.
2025-06-10T12:22:25.207267Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.207526Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.207788Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.208844Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi10\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:25.209869Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.210683Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.211177Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi10/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.211784Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi10/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:25.212683Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.213003Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.213295Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.213668Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi10\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:25.214069Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.214347Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.215000Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi10/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.215652Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi10/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:25.216230Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.216503Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.216783Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.217329Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi10\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:25.217683Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.218033Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.218460Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi10/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.219094Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi10/wp_termmeta` because it could not be opened.
2025-06-10T12:22:25.219499Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.219763Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.220107Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.220492Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi10\wp_terms.ibd' OS error: 103
2025-06-10T12:22:25.220807Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.221133Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.221549Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi10/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.222153Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi10/wp_terms` because it could not be opened.
2025-06-10T12:22:25.222517Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.222780Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.223117Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.223497Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi10\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:25.223819Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.224145Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.224557Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi10/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.225186Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi10/wp_usermeta` because it could not be opened.
2025-06-10T12:22:25.225568Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.225829Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.226158Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.226535Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi10\wp_users.ibd' OS error: 103
2025-06-10T12:22:25.226845Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.227204Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.227617Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi10/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.228225Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi10/wp_users` because it could not be opened.
2025-06-10T12:22:25.228659Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.228987Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.229276Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.229652Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi10\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:25.230061Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.230317Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.230720Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi10/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.231361Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi10/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:25.231753Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.232070Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.232337Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.232708Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi10\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:25.233156Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.233535Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.234075Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi10/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.234656Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi10/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:25.235149Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.235503Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.235769Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.236244Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi10\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:25.236565Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.236911Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.237413Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi10/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.238068Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi10/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:25.238455Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.238710Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.239074Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.239437Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi10\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:25.240111Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.240989Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.241907Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi10/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.242923Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi10/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:25.244385Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.244775Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.245096Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.245511Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi2\wp_ahm_asset_links.ibd' OS error: 103
2025-06-10T12:22:25.245852Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.246115Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.246618Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi2/wp_ahm_asset_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.247212Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi2/wp_ahm_asset_links` because it could not be opened.
2025-06-10T12:22:25.248086Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.248413Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.248739Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.249133Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi2\wp_ahm_assets.ibd' OS error: 103
2025-06-10T12:22:25.249522Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.249813Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.250266Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi2/wp_ahm_assets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.251093Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi2/wp_ahm_assets` because it could not be opened.
2025-06-10T12:22:25.251553Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.251832Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.252109Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.252536Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi2\wp_ahm_download_stats.ibd' OS error: 103
2025-06-10T12:22:25.252881Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.253146Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.253591Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi2/wp_ahm_download_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.254246Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi2/wp_ahm_download_stats` because it could not be opened.
2025-06-10T12:22:25.254702Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.255027Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.255310Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.255714Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi2\wp_ahm_emails.ibd' OS error: 103
2025-06-10T12:22:25.256038Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.256298Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.256774Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi2/wp_ahm_emails`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.257339Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi2/wp_ahm_emails` because it could not be opened.
2025-06-10T12:22:25.257771Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.258039Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.258310Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.258742Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi2\wp_ahm_sessions.ibd' OS error: 103
2025-06-10T12:22:25.259070Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.259330Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.259815Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi2/wp_ahm_sessions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.260534Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi2/wp_ahm_sessions` because it could not be opened.
2025-06-10T12:22:25.260920Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.261181Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.261509Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.262055Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi2\wp_ahm_social_conns.ibd' OS error: 103
2025-06-10T12:22:25.262446Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.262718Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.263130Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi2/wp_ahm_social_conns`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.263833Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi2/wp_ahm_social_conns` because it could not be opened.
2025-06-10T12:22:25.264284Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.264607Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.264877Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.265252Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi2\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:25.265660Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.265910Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.266303Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi2/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.266926Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi2/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:25.267294Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.267598Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.267889Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.268257Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi2\wp_comments.ibd' OS error: 103
2025-06-10T12:22:25.268625Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.268879Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.269275Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi2/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.269866Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi2/wp_comments` because it could not be opened.
2025-06-10T12:22:25.270233Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.270568Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.270841Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.271210Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi2\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:25.271997Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.272461Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.272931Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi2/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.273500Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi2/wp_fbv` because it could not be opened.
2025-06-10T12:22:25.273890Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.274140Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.274489Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.274901Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi2\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:25.275317Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.275702Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.276117Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi2/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.276739Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi2/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:25.277170Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.277466Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.277741Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.278122Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi2\wp_links.ibd' OS error: 103
2025-06-10T12:22:25.278481Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.278748Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.279165Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi2/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.279809Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi2/wp_links` because it could not be opened.
2025-06-10T12:22:25.280257Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.280580Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.280838Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.281220Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi2\wp_msw_stocks.ibd' OS error: 103
2025-06-10T12:22:25.281616Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.281869Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.282269Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi2/wp_msw_stocks`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.282935Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi2/wp_msw_stocks` because it could not be opened.
2025-06-10T12:22:25.283334Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.283635Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.283895Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.284269Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi2\wp_newsletter.ibd' OS error: 103
2025-06-10T12:22:25.284686Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.285029Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.285578Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi2/wp_newsletter`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.286151Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi2/wp_newsletter` because it could not be opened.
2025-06-10T12:22:25.286662Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.287175Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.288137Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.288631Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi2\wp_newsletter_emails.ibd' OS error: 103
2025-06-10T12:22:25.289106Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.289619Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.290163Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi2/wp_newsletter_emails`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.290780Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi2/wp_newsletter_emails` because it could not be opened.
2025-06-10T12:22:25.291275Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.291547Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.291825Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.292273Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi2\wp_newsletter_sent.ibd' OS error: 103
2025-06-10T12:22:25.292648Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.292920Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.293373Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi2/wp_newsletter_sent`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.293951Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi2/wp_newsletter_sent` because it could not be opened.
2025-06-10T12:22:25.294546Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.294836Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.295166Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.295599Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi2\wp_newsletter_stats.ibd' OS error: 103
2025-06-10T12:22:25.295963Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.296282Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.296704Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi2/wp_newsletter_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.297345Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi2/wp_newsletter_stats` because it could not be opened.
2025-06-10T12:22:25.297780Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.298028Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.298401Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.298923Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi2\wp_newsletter_user_logs.ibd' OS error: 103
2025-06-10T12:22:25.299328Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.299580Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.299968Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi2/wp_newsletter_user_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.300782Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi2/wp_newsletter_user_logs` because it could not be opened.
2025-06-10T12:22:25.301286Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.301560Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.301827Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.302283Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi2\wp_options.ibd' OS error: 103
2025-06-10T12:22:25.302601Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.302855Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.303317Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi2/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.303849Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi2/wp_options` because it could not be opened.
2025-06-10T12:22:25.304313Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.304569Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.304831Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.305337Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi2\wp_post_views.ibd' OS error: 103
2025-06-10T12:22:25.305649Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.305905Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.306399Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi2/wp_post_views`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.306934Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi2/wp_post_views` because it could not be opened.
2025-06-10T12:22:25.307632Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.307911Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.308275Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.308644Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi2\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:25.308957Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.309271Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.309667Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi2/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.310324Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi2/wp_postmeta` because it could not be opened.
2025-06-10T12:22:25.310700Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.310957Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.311294Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.311659Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi2\wp_posts.ibd' OS error: 103
2025-06-10T12:22:25.311963Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.312309Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.312703Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi2/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.313480Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi2/wp_posts` because it could not be opened.
2025-06-10T12:22:25.314005Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.314307Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.314587Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.314971Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi2\wp_revslider_css.ibd' OS error: 103
2025-06-10T12:22:25.315375Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.315642Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.316115Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi2/wp_revslider_css`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.316717Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi2/wp_revslider_css` because it could not be opened.
2025-06-10T12:22:25.317247Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.317502Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.317760Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.318291Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi2\wp_revslider_css_bkp.ibd' OS error: 103
2025-06-10T12:22:25.318616Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.318863Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.319487Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi2/wp_revslider_css_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.320224Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi2/wp_revslider_css_bkp` because it could not be opened.
2025-06-10T12:22:25.320816Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.321274Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.321925Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.322331Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi2\wp_revslider_layer_animations.ibd' OS error: 103
2025-06-10T12:22:25.322739Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.323010Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.323500Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi2/wp_revslider_layer_animations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.324100Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi2/wp_revslider_layer_animations` because it could not be opened.
2025-06-10T12:22:25.324609Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.324874Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.325144Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.325753Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi2\wp_revslider_layer_animations_bkp.ibd' OS error: 103
2025-06-10T12:22:25.326179Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.326463Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.326904Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi2/wp_revslider_layer_animations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.327645Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi2/wp_revslider_layer_animations_bkp` because it could not be opened.
2025-06-10T12:22:25.328125Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.328471Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.328751Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.329138Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi2\wp_revslider_navigations.ibd' OS error: 103
2025-06-10T12:22:25.329757Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.330153Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.330642Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi2/wp_revslider_navigations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.331233Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi2/wp_revslider_navigations` because it could not be opened.
2025-06-10T12:22:25.331725Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.331992Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.332321Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.332720Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi2\wp_revslider_navigations_bkp.ibd' OS error: 103
2025-06-10T12:22:25.333076Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.333382Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.333796Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi2/wp_revslider_navigations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.334523Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi2/wp_revslider_navigations_bkp` because it could not be opened.
2025-06-10T12:22:25.334941Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.335207Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.335532Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.335912Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi2\wp_revslider_sliders.ibd' OS error: 103
2025-06-10T12:22:25.336283Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.336555Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.336963Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi2/wp_revslider_sliders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.337570Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi2/wp_revslider_sliders` because it could not be opened.
2025-06-10T12:22:25.337946Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.338210Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.338520Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.338954Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi2\wp_revslider_sliders_bkp.ibd' OS error: 103
2025-06-10T12:22:25.339323Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.339584Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.340000Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi2/wp_revslider_sliders_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.340639Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi2/wp_revslider_sliders_bkp` because it could not be opened.
2025-06-10T12:22:25.341027Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.341355Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.341626Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.342007Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi2\wp_revslider_slides.ibd' OS error: 103
2025-06-10T12:22:25.342402Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.342664Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.343075Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi2/wp_revslider_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.343709Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi2/wp_revslider_slides` because it could not be opened.
2025-06-10T12:22:25.344098Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.344427Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.344799Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.345268Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi2\wp_revslider_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:25.345629Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.345897Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.346384Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi2/wp_revslider_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.346977Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi2/wp_revslider_slides_bkp` because it could not be opened.
2025-06-10T12:22:25.347430Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.347696Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.347966Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.348384Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi2\wp_revslider_static_slides.ibd' OS error: 103
2025-06-10T12:22:25.348744Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.349028Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.349474Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi2/wp_revslider_static_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.350067Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi2/wp_revslider_static_slides` because it could not be opened.
2025-06-10T12:22:25.350523Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.350905Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.351187Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.351616Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi2\wp_revslider_static_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:25.352360Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.353463Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.354540Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi2/wp_revslider_static_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.355237Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi2/wp_revslider_static_slides_bkp` because it could not be opened.
2025-06-10T12:22:25.355706Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.356009Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.356278Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.356658Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi2\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:25.357044Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.357311Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.357754Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi2/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.358354Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi2/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:25.358857Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.359132Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.359408Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.359840Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi2\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:25.360174Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.360527Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.361080Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi2/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.361661Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi2/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:25.362352Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.362657Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.362987Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.363353Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi2\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:25.363659Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.363996Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.364431Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi2/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.365091Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi2/wp_termmeta` because it could not be opened.
2025-06-10T12:22:25.365468Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.365759Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.366063Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.366423Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi2\wp_terms.ibd' OS error: 103
2025-06-10T12:22:25.366758Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.367063Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.367451Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi2/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.368157Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi2/wp_terms` because it could not be opened.
2025-06-10T12:22:25.368525Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.368875Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.369148Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.369514Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi2\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:25.369883Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.370135Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.370525Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi2/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.371305Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi2/wp_usermeta` because it could not be opened.
2025-06-10T12:22:25.371695Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.372102Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.372490Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.372966Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi2\wp_users.ibd' OS error: 103
2025-06-10T12:22:25.373301Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.373543Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.374015Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi2/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.374543Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi2/wp_users` because it could not be opened.
2025-06-10T12:22:25.374974Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.375226Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.375486Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.375922Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi2\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:25.376252Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.376502Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.377024Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi2/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.377616Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi2/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:25.378121Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.378377Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.378636Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.379093Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi2\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:25.379402Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.379650Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.380119Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi2/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.380746Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi2/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:25.381153Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.381463Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.381810Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.382240Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi2\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:25.382546Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.382919Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.383324Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi2/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.384431Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi2/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:25.385852Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.386131Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.386488Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.386889Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi2\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:25.387258Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.387547Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.387978Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi2/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.388648Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi2/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:25.389097Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.389410Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.389840Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.390233Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi3\wp_ahm_asset_links.ibd' OS error: 103
2025-06-10T12:22:25.390618Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.390884Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.391363Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi3/wp_ahm_asset_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.391952Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi3/wp_ahm_asset_links` because it could not be opened.
2025-06-10T12:22:25.392444Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.392727Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.393059Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.393651Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi3\wp_ahm_assets.ibd' OS error: 103
2025-06-10T12:22:25.394037Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.394340Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.394752Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi3/wp_ahm_assets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.395381Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi3/wp_ahm_assets` because it could not be opened.
2025-06-10T12:22:25.395799Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.396058Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.396361Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.396816Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi3\wp_ahm_download_stats.ibd' OS error: 103
2025-06-10T12:22:25.397193Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.397559Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.397971Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi3/wp_ahm_download_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.398651Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi3/wp_ahm_download_stats` because it could not be opened.
2025-06-10T12:22:25.399044Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.399372Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.399657Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.400023Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi3\wp_ahm_emails.ibd' OS error: 103
2025-06-10T12:22:25.400455Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.400757Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.401154Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi3/wp_ahm_emails`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.401883Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi3/wp_ahm_emails` because it could not be opened.
2025-06-10T12:22:25.402264Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.402583Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.402846Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.403216Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi3\wp_ahm_sessions.ibd' OS error: 103
2025-06-10T12:22:25.403666Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.403940Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.404416Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi3/wp_ahm_sessions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.404998Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi3/wp_ahm_sessions` because it could not be opened.
2025-06-10T12:22:25.405442Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.405714Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.405988Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.406421Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi3\wp_ahm_social_conns.ibd' OS error: 103
2025-06-10T12:22:25.406773Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.407039Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.407485Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi3/wp_ahm_social_conns`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.408070Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi3/wp_ahm_social_conns` because it could not be opened.
2025-06-10T12:22:25.408512Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.408803Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.409112Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.409570Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi3\wp_cf7_vdata.ibd' OS error: 103
2025-06-10T12:22:25.409913Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.410340Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.411145Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi3/wp_cf7_vdata`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.412330Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi3/wp_cf7_vdata` because it could not be opened.
2025-06-10T12:22:25.413067Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.413399Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.413689Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.414158Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi3\wp_cf7_vdata_entry.ibd' OS error: 103
2025-06-10T12:22:25.414528Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.414796Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.415223Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi3/wp_cf7_vdata_entry`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.415827Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi3/wp_cf7_vdata_entry` because it could not be opened.
2025-06-10T12:22:25.416279Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.416554Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.416849Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.417278Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi3\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:25.417652Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.417952Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.418508Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi3/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.419320Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi3/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:25.420132Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.420512Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.420913Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.421342Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi3\wp_comments.ibd' OS error: 103
2025-06-10T12:22:25.421673Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.421942Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.422400Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi3/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.422964Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi3/wp_comments` because it could not be opened.
2025-06-10T12:22:25.423425Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.423702Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.423982Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.424434Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi3\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:25.424760Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.425026Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.425495Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi3/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.426577Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi3/wp_fbv` because it could not be opened.
2025-06-10T12:22:25.427124Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.427436Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.428053Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.428780Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi3\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:25.429243Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.429629Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.430383Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi3/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.431179Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi3/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:25.431882Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.432150Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.432488Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.433128Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi3\wp_links.ibd' OS error: 103
2025-06-10T12:22:25.433456Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.433968Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.434409Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi3/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.435209Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi3/wp_links` because it could not be opened.
2025-06-10T12:22:25.435789Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.436161Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.436439Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.436958Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi3\wp_msw_stocks.ibd' OS error: 103
2025-06-10T12:22:25.437328Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.437685Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.438146Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi3/wp_msw_stocks`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.438851Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi3/wp_msw_stocks` because it could not be opened.
2025-06-10T12:22:25.439310Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.439567Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.440061Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.440451Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi3\wp_newsletter.ibd' OS error: 103
2025-06-10T12:22:25.440837Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.441142Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.441583Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi3/wp_newsletter`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.442241Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi3/wp_newsletter` because it could not be opened.
2025-06-10T12:22:25.442706Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.442988Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.443260Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.443680Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi3\wp_newsletter_emails.ibd' OS error: 103
2025-06-10T12:22:25.444057Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.444331Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.444854Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi3/wp_newsletter_emails`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.445474Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi3/wp_newsletter_emails` because it could not be opened.
2025-06-10T12:22:25.446018Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.446277Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.446545Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.446988Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi3\wp_newsletter_sent.ibd' OS error: 103
2025-06-10T12:22:25.447344Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.447735Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.448351Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi3/wp_newsletter_sent`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.449054Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi3/wp_newsletter_sent` because it could not be opened.
2025-06-10T12:22:25.450747Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.451343Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.451858Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.452405Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi3\wp_newsletter_stats.ibd' OS error: 103
2025-06-10T12:22:25.452856Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.453122Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.453652Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi3/wp_newsletter_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.454394Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi3/wp_newsletter_stats` because it could not be opened.
2025-06-10T12:22:25.455030Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.455321Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.455685Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.456102Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi3\wp_newsletter_user_logs.ibd' OS error: 103
2025-06-10T12:22:25.456487Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.456844Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.457276Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi3/wp_newsletter_user_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.458151Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi3/wp_newsletter_user_logs` because it could not be opened.
2025-06-10T12:22:25.458904Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.459268Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.459649Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.460272Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi3\wp_options.ibd' OS error: 103
2025-06-10T12:22:25.460681Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.460955Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.461385Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi3/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.462086Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi3/wp_options` because it could not be opened.
2025-06-10T12:22:25.462607Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.462923Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.463207Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.463681Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi3\wp_post_views.ibd' OS error: 103
2025-06-10T12:22:25.464055Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.464387Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.464878Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi3/wp_post_views`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.465508Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi3/wp_post_views` because it could not be opened.
2025-06-10T12:22:25.466078Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.466580Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.467187Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.468014Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi3\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:25.468580Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.468923Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.469361Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi3/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.470100Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi3/wp_postmeta` because it could not be opened.
2025-06-10T12:22:25.470634Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.470942Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.471485Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.473132Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi3\wp_posts.ibd' OS error: 103
2025-06-10T12:22:25.473714Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.474188Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.474755Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi3/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.475354Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi3/wp_posts` because it could not be opened.
2025-06-10T12:22:25.475968Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.476308Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.476939Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.477607Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi3\wp_redirection_404.ibd' OS error: 103
2025-06-10T12:22:25.478023Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.478321Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.478874Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi3/wp_redirection_404`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.479574Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi3/wp_redirection_404` because it could not be opened.
2025-06-10T12:22:25.480544Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.481151Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.481580Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.482330Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi3\wp_redirection_groups.ibd' OS error: 103
2025-06-10T12:22:25.483478Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.483995Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.484535Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi3/wp_redirection_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.485146Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi3/wp_redirection_groups` because it could not be opened.
2025-06-10T12:22:25.485643Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.485931Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.486212Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.486670Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi3\wp_redirection_items.ibd' OS error: 103
2025-06-10T12:22:25.487053Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.487335Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.487909Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi3/wp_redirection_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.488564Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi3/wp_redirection_items` because it could not be opened.
2025-06-10T12:22:25.489105Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.489487Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.489832Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.490237Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi3\wp_redirection_logs.ibd' OS error: 103
2025-06-10T12:22:25.490653Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.490938Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.491352Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi3/wp_redirection_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.492018Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi3/wp_redirection_logs` because it could not be opened.
2025-06-10T12:22:25.492626Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.492910Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.493184Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.493658Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi3\wp_revslider_css.ibd' OS error: 103
2025-06-10T12:22:25.494028Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.494343Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.495012Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi3/wp_revslider_css`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.496122Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi3/wp_revslider_css` because it could not be opened.
2025-06-10T12:22:25.496713Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.497060Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.497574Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.498058Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi3\wp_revslider_css_bkp.ibd' OS error: 103
2025-06-10T12:22:25.498406Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.498705Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.499128Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi3/wp_revslider_css_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.499750Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi3/wp_revslider_css_bkp` because it could not be opened.
2025-06-10T12:22:25.500188Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.500492Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.500784Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.501276Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi3\wp_revslider_layer_animations.ibd' OS error: 103
2025-06-10T12:22:25.501676Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.501943Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.502359Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi3/wp_revslider_layer_animations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.503024Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi3/wp_revslider_layer_animations` because it could not be opened.
2025-06-10T12:22:25.503626Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.503909Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.504212Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.504622Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi3\wp_revslider_layer_animations_bkp.ibd' OS error: 103
2025-06-10T12:22:25.505007Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.505276Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.505734Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi3/wp_revslider_layer_animations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.506354Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi3/wp_revslider_layer_animations_bkp` because it could not be opened.
2025-06-10T12:22:25.506844Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.507308Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.507669Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.508083Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi3\wp_revslider_navigations.ibd' OS error: 103
2025-06-10T12:22:25.508537Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.508832Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.509309Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi3/wp_revslider_navigations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.510024Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi3/wp_revslider_navigations` because it could not be opened.
2025-06-10T12:22:25.510540Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.510826Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.511105Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.511775Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi3\wp_revslider_navigations_bkp.ibd' OS error: 103
2025-06-10T12:22:25.512240Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.512514Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.512962Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi3/wp_revslider_navigations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.513755Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi3/wp_revslider_navigations_bkp` because it could not be opened.
2025-06-10T12:22:25.514659Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.514963Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.515312Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.515713Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi3\wp_revslider_sliders.ibd' OS error: 103
2025-06-10T12:22:25.516059Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.516364Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.516849Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi3/wp_revslider_sliders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.517581Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi3/wp_revslider_sliders` because it could not be opened.
2025-06-10T12:22:25.518098Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.518816Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.519124Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.519617Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi3\wp_revslider_sliders_bkp.ibd' OS error: 103
2025-06-10T12:22:25.519990Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.520323Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.520759Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi3/wp_revslider_sliders_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.521471Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi3/wp_revslider_sliders_bkp` because it could not be opened.
2025-06-10T12:22:25.521963Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.522313Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.522602Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.522987Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi3\wp_revslider_slides.ibd' OS error: 103
2025-06-10T12:22:25.523387Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.523650Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.524068Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi3/wp_revslider_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.524682Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi3/wp_revslider_slides` because it could not be opened.
2025-06-10T12:22:25.525111Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.525395Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.525665Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.526047Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi3\wp_revslider_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:25.526438Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.526705Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.527123Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi3/wp_revslider_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.527756Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi3/wp_revslider_slides_bkp` because it could not be opened.
2025-06-10T12:22:25.528174Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.528470Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.528847Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.529379Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi3\wp_revslider_static_slides.ibd' OS error: 103
2025-06-10T12:22:25.529807Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.530066Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.530679Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi3/wp_revslider_static_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.531443Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi3/wp_revslider_static_slides` because it could not be opened.
2025-06-10T12:22:25.531910Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.532294Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.532933Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.533621Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi3\wp_revslider_static_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:25.534213Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.534597Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.535239Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi3/wp_revslider_static_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.535871Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi3/wp_revslider_static_slides_bkp` because it could not be opened.
2025-06-10T12:22:25.536379Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.536654Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.537049Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.537732Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi3\wp_sbi_instagram_feeds_posts.ibd' OS error: 103
2025-06-10T12:22:25.538142Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.538488Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.538918Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi3/wp_sbi_instagram_feeds_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.539726Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi3/wp_sbi_instagram_feeds_posts` because it could not be opened.
2025-06-10T12:22:25.540540Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.540964Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.541491Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.542199Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi3\wp_sbi_instagram_posts.ibd' OS error: 103
2025-06-10T12:22:25.542676Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.543102Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.545689Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi3/wp_sbi_instagram_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.547516Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi3/wp_sbi_instagram_posts` because it could not be opened.
2025-06-10T12:22:25.548101Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.548642Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.549155Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.549804Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi3\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:25.551053Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.551405Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.552338Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi3/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.556462Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi3/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:25.558352Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.558981Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.561299Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.561947Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi3\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:25.562508Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.563576Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.564704Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi3/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.565547Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi3/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:25.566182Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.566747Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.567305Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.567743Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi3\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:25.568643Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.569319Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.570162Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi3/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.571183Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi3/wp_termmeta` because it could not be opened.
2025-06-10T12:22:25.573460Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.573811Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.574828Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.575796Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi3\wp_terms.ibd' OS error: 103
2025-06-10T12:22:25.576309Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.576679Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.577221Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi3/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.577839Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi3/wp_terms` because it could not be opened.
2025-06-10T12:22:25.578366Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.578726Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.579060Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.579563Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi3\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:25.580301Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.580719Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.581263Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi3/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.582220Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi3/wp_usermeta` because it could not be opened.
2025-06-10T12:22:25.582922Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.583236Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.583574Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.584331Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi3\wp_users.ibd' OS error: 103
2025-06-10T12:22:25.584785Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.585062Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.585622Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi3/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.587199Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi3/wp_users` because it could not be opened.
2025-06-10T12:22:25.587642Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.588006Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.588352Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.589060Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi3\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:25.589588Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.589875Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.590421Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi3/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.591172Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi3/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:25.591631Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.591931Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.592302Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.593399Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi3\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:25.593803Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.594265Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.594956Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi3/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.595794Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi3/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:25.596246Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.596570Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.596890Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.597284Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi3\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:25.597622Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.597911Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.598336Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi3/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.598947Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi3/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:25.599403Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.599721Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.599999Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.600422Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi3\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:25.600817Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.601099Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.601580Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi3/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.602220Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi3/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:25.602710Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.602986Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.603283Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.603689Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi4\wp_ahm_asset_links.ibd' OS error: 103
2025-06-10T12:22:25.604031Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.604295Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.604748Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi4/wp_ahm_asset_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.605348Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi4/wp_ahm_asset_links` because it could not be opened.
2025-06-10T12:22:25.605771Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.606044Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.606316Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.606743Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi4\wp_ahm_assets.ibd' OS error: 103
2025-06-10T12:22:25.607075Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.607341Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.607836Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi4/wp_ahm_assets`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.608512Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi4/wp_ahm_assets` because it could not be opened.
2025-06-10T12:22:25.608993Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.609271Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.609553Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.609995Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi4\wp_ahm_download_stats.ibd' OS error: 103
2025-06-10T12:22:25.610337Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.610662Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.611085Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi4/wp_ahm_download_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.611724Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi4/wp_ahm_download_stats` because it could not be opened.
2025-06-10T12:22:25.612133Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.612399Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.612746Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.613138Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi4\wp_ahm_emails.ibd' OS error: 103
2025-06-10T12:22:25.613469Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.613804Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.614224Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi4/wp_ahm_emails`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.614869Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi4/wp_ahm_emails` because it could not be opened.
2025-06-10T12:22:25.615314Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.615624Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.615956Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.616353Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi4\wp_ahm_sessions.ibd' OS error: 103
2025-06-10T12:22:25.616733Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.617005Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.617424Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi4/wp_ahm_sessions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.618054Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi4/wp_ahm_sessions` because it could not be opened.
2025-06-10T12:22:25.618467Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.618780Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.619055Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.619446Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi4\wp_ahm_social_conns.ibd' OS error: 103
2025-06-10T12:22:25.619841Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.620119Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.620608Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi4/wp_ahm_social_conns`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.621427Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi4/wp_ahm_social_conns` because it could not be opened.
2025-06-10T12:22:25.621966Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.622264Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.622818Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.623264Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi4\wp_cf7_vdata.ibd' OS error: 103
2025-06-10T12:22:25.624017Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.624698Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.625867Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi4/wp_cf7_vdata`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.626584Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi4/wp_cf7_vdata` because it could not be opened.
2025-06-10T12:22:25.627035Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.627404Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.627748Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.628165Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi4\wp_cf7_vdata_entry.ibd' OS error: 103
2025-06-10T12:22:25.628536Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.628806Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.629259Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi4/wp_cf7_vdata_entry`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.629854Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi4/wp_cf7_vdata_entry` because it could not be opened.
2025-06-10T12:22:25.630359Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.630660Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.630990Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.631436Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi4\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:25.631772Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.632120Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.632653Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi4/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.633318Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi4/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:25.635292Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.635725Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.636479Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.637005Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi4\wp_comments.ibd' OS error: 103
2025-06-10T12:22:25.637827Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.638194Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.638680Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi4/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.639444Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi4/wp_comments` because it could not be opened.
2025-06-10T12:22:25.639885Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.640228Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.640642Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.641053Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi4\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:25.641432Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.641753Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.642343Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi4/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.642915Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi4/wp_fbv` because it could not be opened.
2025-06-10T12:22:25.643372Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.643654Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.643937Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.644383Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi4\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:25.644732Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.644997Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.645490Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi4/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.646088Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi4/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:25.646569Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.646843Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.647152Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.647549Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi4\wp_links.ibd' OS error: 103
2025-06-10T12:22:25.647868Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.648169Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.648586Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi4/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.649199Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi4/wp_links` because it could not be opened.
2025-06-10T12:22:25.649591Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.649859Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.650256Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.650794Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi4\wp_msw_stocks.ibd' OS error: 103
2025-06-10T12:22:25.651203Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.651494Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.651918Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi4/wp_msw_stocks`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.652537Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi4/wp_msw_stocks` because it could not be opened.
2025-06-10T12:22:25.652957Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.653380Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.653783Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.654264Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi4\wp_newsletter.ibd' OS error: 103
2025-06-10T12:22:25.654653Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.654929Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.655422Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi4/wp_newsletter`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.655995Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi4/wp_newsletter` because it could not be opened.
2025-06-10T12:22:25.656526Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.656788Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.657215Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.657689Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi4\wp_newsletter_emails.ibd' OS error: 103
2025-06-10T12:22:25.658110Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.658618Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.659195Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi4/wp_newsletter_emails`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.659801Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi4/wp_newsletter_emails` because it could not be opened.
2025-06-10T12:22:25.660305Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.660581Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.660863Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.661247Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi4\wp_newsletter_sent.ibd' OS error: 103
2025-06-10T12:22:25.661698Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.662037Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.662516Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi4/wp_newsletter_sent`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.663141Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi4/wp_newsletter_sent` because it could not be opened.
2025-06-10T12:22:25.663558Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.663895Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.664159Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.664625Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi4\wp_newsletter_stats.ibd' OS error: 103
2025-06-10T12:22:25.665019Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.665278Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.665768Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi4/wp_newsletter_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.666553Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi4/wp_newsletter_stats` because it could not be opened.
2025-06-10T12:22:25.667666Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.668208Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.668677Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.669334Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi4\wp_newsletter_user_logs.ibd' OS error: 103
2025-06-10T12:22:25.669797Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.670106Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.670809Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi4/wp_newsletter_user_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.671909Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi4/wp_newsletter_user_logs` because it could not be opened.
2025-06-10T12:22:25.672676Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.673017Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.673325Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.673751Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi4\wp_options.ibd' OS error: 103
2025-06-10T12:22:25.674074Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.674338Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.674846Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi4/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.675446Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi4/wp_options` because it could not be opened.
2025-06-10T12:22:25.675936Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.676209Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.676507Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.676916Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi4\wp_post_views.ibd' OS error: 103
2025-06-10T12:22:25.677366Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.677711Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.678162Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi4/wp_post_views`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.678757Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi4/wp_post_views` because it could not be opened.
2025-06-10T12:22:25.679181Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.679461Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.679786Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.680174Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi4\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:25.680496Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.680807Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.681232Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi4/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.681829Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi4/wp_postmeta` because it could not be opened.
2025-06-10T12:22:25.682386Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.682718Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.683013Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.683603Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi4\wp_posts.ibd' OS error: 103
2025-06-10T12:22:25.683955Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.684233Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.684738Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi4/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.685637Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi4/wp_posts` because it could not be opened.
2025-06-10T12:22:25.686178Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.686463Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.686810Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.687204Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi4\wp_revslider_css.ibd' OS error: 103
2025-06-10T12:22:25.687572Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.687847Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.688256Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi4/wp_revslider_css`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.688858Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi4/wp_revslider_css` because it could not be opened.
2025-06-10T12:22:25.689283Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.689596Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.689895Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.690278Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi4\wp_revslider_css_bkp.ibd' OS error: 103
2025-06-10T12:22:25.690787Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.691097Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.691813Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi4/wp_revslider_css_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.692748Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi4/wp_revslider_css_bkp` because it could not be opened.
2025-06-10T12:22:25.693452Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.693726Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.693988Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.694607Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi4\wp_revslider_layer_animations.ibd' OS error: 103
2025-06-10T12:22:25.694961Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.695293Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.695820Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi4/wp_revslider_layer_animations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.696470Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi4/wp_revslider_layer_animations` because it could not be opened.
2025-06-10T12:22:25.696973Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.697249Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.697695Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.698487Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi4\wp_revslider_layer_animations_bkp.ibd' OS error: 103
2025-06-10T12:22:25.699059Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.699469Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.700036Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi4/wp_revslider_layer_animations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.700810Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi4/wp_revslider_layer_animations_bkp` because it could not be opened.
2025-06-10T12:22:25.701520Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.701867Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.702164Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.702604Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi4\wp_revslider_navigations.ibd' OS error: 103
2025-06-10T12:22:25.702996Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.703346Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.703835Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi4/wp_revslider_navigations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.704604Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi4/wp_revslider_navigations` because it could not be opened.
2025-06-10T12:22:25.705124Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.705522Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.705813Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.706210Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi4\wp_revslider_navigations_bkp.ibd' OS error: 103
2025-06-10T12:22:25.706679Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.706949Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.707475Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi4/wp_revslider_navigations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.708088Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi4/wp_revslider_navigations_bkp` because it could not be opened.
2025-06-10T12:22:25.708649Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.708914Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.709177Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.709787Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi4\wp_revslider_sliders.ibd' OS error: 103
2025-06-10T12:22:25.710280Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.710648Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.711046Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi4/wp_revslider_sliders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.711798Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi4/wp_revslider_sliders` because it could not be opened.
2025-06-10T12:22:25.712230Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.712652Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.712920Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.713295Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi4\wp_revslider_sliders_bkp.ibd' OS error: 103
2025-06-10T12:22:25.713730Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.713983Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.714508Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi4/wp_revslider_sliders_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.715353Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi4/wp_revslider_sliders_bkp` because it could not be opened.
2025-06-10T12:22:25.715864Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.716142Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.716484Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.716873Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi4\wp_revslider_slides.ibd' OS error: 103
2025-06-10T12:22:25.717217Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.717543Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.718054Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi4/wp_revslider_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.718808Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi4/wp_revslider_slides` because it could not be opened.
2025-06-10T12:22:25.719338Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.719682Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.719953Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.720380Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi4\wp_revslider_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:25.720747Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.721001Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.721472Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi4/wp_revslider_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.722972Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi4/wp_revslider_slides_bkp` because it could not be opened.
2025-06-10T12:22:25.723558Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.723974Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.724257Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.724756Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi4\wp_revslider_static_slides.ibd' OS error: 103
2025-06-10T12:22:25.725110Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.725375Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.725840Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi4/wp_revslider_static_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.726455Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi4/wp_revslider_static_slides` because it could not be opened.
2025-06-10T12:22:25.726943Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.727221Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.727500Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.727896Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi4\wp_revslider_static_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:25.728259Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.728522Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.728993Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi4/wp_revslider_static_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.729648Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi4/wp_revslider_static_slides_bkp` because it could not be opened.
2025-06-10T12:22:25.730202Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.730481Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.730798Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.731190Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi4\wp_sbi_instagram_feeds_posts.ibd' OS error: 103
2025-06-10T12:22:25.731565Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.731877Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.732302Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi4/wp_sbi_instagram_feeds_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.733060Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi4/wp_sbi_instagram_feeds_posts` because it could not be opened.
2025-06-10T12:22:25.733607Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.733907Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.734212Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.734622Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi4\wp_sbi_instagram_posts.ibd' OS error: 103
2025-06-10T12:22:25.734985Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.735265Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.735943Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi4/wp_sbi_instagram_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.736702Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi4/wp_sbi_instagram_posts` because it could not be opened.
2025-06-10T12:22:25.737147Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.737404Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.737784Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.738153Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi4\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:25.738475Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.738834Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.739225Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi4/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.739956Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi4/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:25.740494Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.740805Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.741063Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.741581Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi4\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:25.741934Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.742261Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.742715Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi4/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.743268Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi4/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:25.743697Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.743999Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.744261Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.744690Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi4\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:25.745003Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.745253Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.745765Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi4/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.746320Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi4/wp_termmeta` because it could not be opened.
2025-06-10T12:22:25.746788Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.747065Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.747326Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.747806Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi4\wp_terms.ibd' OS error: 103
2025-06-10T12:22:25.748131Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.748658Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.749090Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi4/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.749767Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi4/wp_terms` because it could not be opened.
2025-06-10T12:22:25.750173Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.750443Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.750815Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.751218Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi4\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:25.751592Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.751862Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.752280Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi4/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.752904Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi4/wp_usermeta` because it could not be opened.
2025-06-10T12:22:25.753285Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.753617Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.753892Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.754276Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi4\wp_users.ibd' OS error: 103
2025-06-10T12:22:25.754662Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.754928Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.755344Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi4/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.755955Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi4/wp_users` because it could not be opened.
2025-06-10T12:22:25.756319Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.756671Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.756947Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.757338Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi4\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:25.757742Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.758002Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.758410Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi4/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.759058Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi4/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:25.759450Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.759765Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.760181Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.760873Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi4\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:25.761235Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.761566Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.761989Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi4/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.762605Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi4/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:25.763000Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.763271Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.763600Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.764060Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi4\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:25.764424Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.764803Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.765224Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi4/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.765867Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi4/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:25.766277Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.766608Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.766885Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.767554Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_mpi4\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:25.768996Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.769273Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.769770Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_mpi4/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.770811Z 0 [Warning] InnoDB: Ignoring tablespace `client_mpi4/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:25.771693Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.772024Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.772312Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.772791Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech1\wpfjbb_commentmeta.ibd' OS error: 103
2025-06-10T12:22:25.773271Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.773547Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.774000Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech1/wpfjbb_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.774744Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech1/wpfjbb_commentmeta` because it could not be opened.
2025-06-10T12:22:25.775211Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.775477Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.775878Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.776319Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech1\wpfjbb_comments.ibd' OS error: 103
2025-06-10T12:22:25.776695Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.776980Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.777521Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech1/wpfjbb_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.778255Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech1/wpfjbb_comments` because it could not be opened.
2025-06-10T12:22:25.778727Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.779019Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.779296Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.779757Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech1\wpfjbb_links.ibd' OS error: 103
2025-06-10T12:22:25.780114Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.780381Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.780855Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech1/wpfjbb_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.781439Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech1/wpfjbb_links` because it could not be opened.
2025-06-10T12:22:25.781899Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.782156Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.782492Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.782952Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech1\wpfjbb_newsletter.ibd' OS error: 103
2025-06-10T12:22:25.783301Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.783564Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.784011Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech1/wpfjbb_newsletter`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.784594Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech1/wpfjbb_newsletter` because it could not be opened.
2025-06-10T12:22:25.785032Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.785291Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.785553Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.786014Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech1\wpfjbb_newsletter_emails.ibd' OS error: 103
2025-06-10T12:22:25.786360Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.786660Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.787099Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech1/wpfjbb_newsletter_emails`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.787728Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech1/wpfjbb_newsletter_emails` because it could not be opened.
2025-06-10T12:22:25.788145Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.788414Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.788768Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.789157Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech1\wpfjbb_newsletter_sent.ibd' OS error: 103
2025-06-10T12:22:25.789530Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.789811Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.790224Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech1/wpfjbb_newsletter_sent`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.790858Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech1/wpfjbb_newsletter_sent` because it could not be opened.
2025-06-10T12:22:25.791305Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.791623Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.791909Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.792295Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech1\wpfjbb_newsletter_stats.ibd' OS error: 103
2025-06-10T12:22:25.792695Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.792958Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.793377Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech1/wpfjbb_newsletter_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.794013Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech1/wpfjbb_newsletter_stats` because it could not be opened.
2025-06-10T12:22:25.794436Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.794873Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.795190Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.795594Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech1\wpfjbb_newsletter_user_logs.ibd' OS error: 103
2025-06-10T12:22:25.796010Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.796277Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.796776Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech1/wpfjbb_newsletter_user_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.797389Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech1/wpfjbb_newsletter_user_logs` because it could not be opened.
2025-06-10T12:22:25.798253Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.798625Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.798910Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.799489Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech1\wpfjbb_options.ibd' OS error: 103
2025-06-10T12:22:25.800546Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.801363Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.801864Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech1/wpfjbb_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.802589Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech1/wpfjbb_options` because it could not be opened.
2025-06-10T12:22:25.803048Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.803322Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.803770Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.804227Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech1\wpfjbb_postmeta.ibd' OS error: 103
2025-06-10T12:22:25.804576Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.804833Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.805308Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech1/wpfjbb_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.805899Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech1/wpfjbb_postmeta` because it could not be opened.
2025-06-10T12:22:25.806440Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.806723Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.807078Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.807489Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech1\wpfjbb_posts.ibd' OS error: 103
2025-06-10T12:22:25.807818Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.808178Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.808624Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech1/wpfjbb_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.809262Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech1/wpfjbb_posts` because it could not be opened.
2025-06-10T12:22:25.809691Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.809987Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.810270Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.810655Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech1\wpfjbb_revslider_css.ibd' OS error: 103
2025-06-10T12:22:25.811043Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.811333Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.811757Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech1/wpfjbb_revslider_css`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.812364Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech1/wpfjbb_revslider_css` because it could not be opened.
2025-06-10T12:22:25.812812Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.813111Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.813390Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.813778Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech1\wpfjbb_revslider_css_bkp.ibd' OS error: 103
2025-06-10T12:22:25.814196Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.814468Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.814899Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech1/wpfjbb_revslider_css_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.815511Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech1/wpfjbb_revslider_css_bkp` because it could not be opened.
2025-06-10T12:22:25.815967Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.816241Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.816518Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.816932Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech1\wpfjbb_revslider_layer_animations.ibd' OS error: 103
2025-06-10T12:22:25.817322Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.817584Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.818027Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech1/wpfjbb_revslider_layer_animations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.818696Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech1/wpfjbb_revslider_layer_animations` because it could not be opened.
2025-06-10T12:22:25.819181Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.819449Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.819724Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.820154Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech1\wpfjbb_revslider_layer_animations_bkp.ibd' OS error: 103
2025-06-10T12:22:25.820631Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.820931Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.821362Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech1/wpfjbb_revslider_layer_animations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.822103Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech1/wpfjbb_revslider_layer_animations_bkp` because it could not be opened.
2025-06-10T12:22:25.822586Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.823020Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.823305Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.823696Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech1\wpfjbb_revslider_navigations.ibd' OS error: 103
2025-06-10T12:22:25.824164Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.824432Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.824846Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech1/wpfjbb_revslider_navigations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.825498Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech1/wpfjbb_revslider_navigations` because it could not be opened.
2025-06-10T12:22:25.826246Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.826538Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.826813Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.827261Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech1\wpfjbb_revslider_navigations_bkp.ibd' OS error: 103
2025-06-10T12:22:25.827625Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.827946Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.828379Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech1/wpfjbb_revslider_navigations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.829097Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech1/wpfjbb_revslider_navigations_bkp` because it could not be opened.
2025-06-10T12:22:25.829553Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.830014Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.830325Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.830710Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech1\wpfjbb_revslider_sliders.ibd' OS error: 103
2025-06-10T12:22:25.831198Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.831453Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.831947Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech1/wpfjbb_revslider_sliders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.832649Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech1/wpfjbb_revslider_sliders` because it could not be opened.
2025-06-10T12:22:25.833196Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.833796Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.834148Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.834689Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech1\wpfjbb_revslider_sliders_bkp.ibd' OS error: 103
2025-06-10T12:22:25.835159Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.835424Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.835878Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech1/wpfjbb_revslider_sliders_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.836534Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech1/wpfjbb_revslider_sliders_bkp` because it could not be opened.
2025-06-10T12:22:25.837107Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.837367Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.837716Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.838102Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech1\wpfjbb_revslider_slides.ibd' OS error: 103
2025-06-10T12:22:25.838444Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.838791Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.839197Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech1/wpfjbb_revslider_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.839892Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech1/wpfjbb_revslider_slides` because it could not be opened.
2025-06-10T12:22:25.840337Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.840680Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.840994Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.841413Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech1\wpfjbb_revslider_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:25.842059Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.842434Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.843294Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech1/wpfjbb_revslider_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.844062Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech1/wpfjbb_revslider_slides_bkp` because it could not be opened.
2025-06-10T12:22:25.844679Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.844962Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.845228Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.845684Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech1\wpfjbb_revslider_static_slides.ibd' OS error: 103
2025-06-10T12:22:25.846064Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.846323Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.846788Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech1/wpfjbb_revslider_static_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.847370Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech1/wpfjbb_revslider_static_slides` because it could not be opened.
2025-06-10T12:22:25.847870Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.848144Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.848413Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.848999Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech1\wpfjbb_revslider_static_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:25.849367Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.849749Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.850140Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech1/wpfjbb_revslider_static_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.850912Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech1/wpfjbb_revslider_static_slides_bkp` because it could not be opened.
2025-06-10T12:22:25.851407Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.851816Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.852128Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.852486Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech1\wpfjbb_term_relationships.ibd' OS error: 103
2025-06-10T12:22:25.853055Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.853327Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.853797Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech1/wpfjbb_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.854395Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech1/wpfjbb_term_relationships` because it could not be opened.
2025-06-10T12:22:25.854951Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.855205Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.855465Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.855932Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech1\wpfjbb_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:25.856264Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.856577Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.856997Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech1/wpfjbb_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.857703Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech1/wpfjbb_term_taxonomy` because it could not be opened.
2025-06-10T12:22:25.858143Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.858419Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.858761Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.859153Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech1\wpfjbb_termmeta.ibd' OS error: 103
2025-06-10T12:22:25.859491Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.859813Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.860234Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech1/wpfjbb_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.860984Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech1/wpfjbb_termmeta` because it could not be opened.
2025-06-10T12:22:25.861412Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.861758Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.862019Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.862382Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech1\wpfjbb_terms.ibd' OS error: 103
2025-06-10T12:22:25.862773Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.863026Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.863683Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech1/wpfjbb_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.864920Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech1/wpfjbb_terms` because it could not be opened.
2025-06-10T12:22:25.865672Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.865949Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.866328Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.866784Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech1\wpfjbb_usermeta.ibd' OS error: 103
2025-06-10T12:22:25.867141Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.867512Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.867939Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech1/wpfjbb_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.868575Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech1/wpfjbb_usermeta` because it could not be opened.
2025-06-10T12:22:25.869000Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.869324Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.869598Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.869985Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech1\wpfjbb_users.ibd' OS error: 103
2025-06-10T12:22:25.870370Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.870639Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.871070Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech1/wpfjbb_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.871735Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech1/wpfjbb_users` because it could not be opened.
2025-06-10T12:22:25.872256Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.872547Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.872829Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.873354Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech2\wpfjbb_commentmeta.ibd' OS error: 103
2025-06-10T12:22:25.873792Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.874086Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.874619Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech2/wpfjbb_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.875244Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech2/wpfjbb_commentmeta` because it could not be opened.
2025-06-10T12:22:25.875678Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.875938Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.876284Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.876664Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech2\wpfjbb_comments.ibd' OS error: 103
2025-06-10T12:22:25.876993Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.877345Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.877820Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech2/wpfjbb_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.878466Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech2/wpfjbb_comments` because it could not be opened.
2025-06-10T12:22:25.878885Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.879188Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.879466Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.879854Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech2\wpfjbb_links.ibd' OS error: 103
2025-06-10T12:22:25.880290Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.880562Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.880964Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech2/wpfjbb_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.881677Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech2/wpfjbb_links` because it could not be opened.
2025-06-10T12:22:25.882089Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.882386Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.882663Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.883048Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech2\wpfjbb_newsletter.ibd' OS error: 103
2025-06-10T12:22:25.883449Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.883717Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.884165Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech2/wpfjbb_newsletter`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.884747Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech2/wpfjbb_newsletter` because it could not be opened.
2025-06-10T12:22:25.885195Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.885487Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.885761Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.886179Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech2\wpfjbb_newsletter_emails.ibd' OS error: 103
2025-06-10T12:22:25.886536Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.886799Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.887244Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech2/wpfjbb_newsletter_emails`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.887838Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech2/wpfjbb_newsletter_emails` because it could not be opened.
2025-06-10T12:22:25.888299Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.888570Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.888844Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.889261Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech2\wpfjbb_newsletter_sent.ibd' OS error: 103
2025-06-10T12:22:25.889619Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.889886Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.890650Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech2/wpfjbb_newsletter_sent`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.891740Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech2/wpfjbb_newsletter_sent` because it could not be opened.
2025-06-10T12:22:25.892313Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.892579Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.892843Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.893339Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech2\wpfjbb_newsletter_stats.ibd' OS error: 103
2025-06-10T12:22:25.893751Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.894082Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.894621Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech2/wpfjbb_newsletter_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.895275Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech2/wpfjbb_newsletter_stats` because it could not be opened.
2025-06-10T12:22:25.895701Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.895955Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.896325Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.897090Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech2\wpfjbb_newsletter_user_logs.ibd' OS error: 103
2025-06-10T12:22:25.897606Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.898161Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.898633Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech2/wpfjbb_newsletter_user_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.899695Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech2/wpfjbb_newsletter_user_logs` because it could not be opened.
2025-06-10T12:22:25.900319Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.900616Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.900899Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.901312Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech2\wpfjbb_options.ibd' OS error: 103
2025-06-10T12:22:25.901664Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.901942Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.902392Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech2/wpfjbb_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.903073Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech2/wpfjbb_options` because it could not be opened.
2025-06-10T12:22:25.903550Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.903834Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.904188Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.904580Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech2\wpfjbb_postmeta.ibd' OS error: 103
2025-06-10T12:22:25.904923Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.905411Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.905882Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech2/wpfjbb_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.906559Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech2/wpfjbb_postmeta` because it could not be opened.
2025-06-10T12:22:25.907127Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.907450Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.907747Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.908268Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech2\wpfjbb_posts.ibd' OS error: 103
2025-06-10T12:22:25.908636Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.908953Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.909487Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech2/wpfjbb_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.910192Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech2/wpfjbb_posts` because it could not be opened.
2025-06-10T12:22:25.910648Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.910907Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.911188Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.911561Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech2\wpfjbb_revslider_css.ibd' OS error: 103
2025-06-10T12:22:25.911896Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.912275Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.912770Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech2/wpfjbb_revslider_css`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.913483Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech2/wpfjbb_revslider_css` because it could not be opened.
2025-06-10T12:22:25.913872Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.914224Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.914535Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.914976Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech2\wpfjbb_revslider_css_bkp.ibd' OS error: 103
2025-06-10T12:22:25.915376Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.915631Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.916219Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech2/wpfjbb_revslider_css_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.916826Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech2/wpfjbb_revslider_css_bkp` because it could not be opened.
2025-06-10T12:22:25.917317Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.917578Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.917842Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.918366Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech2\wpfjbb_revslider_layer_animations.ibd' OS error: 103
2025-06-10T12:22:25.918932Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.919218Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.919615Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech2/wpfjbb_revslider_layer_animations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.920357Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech2/wpfjbb_revslider_layer_animations` because it could not be opened.
2025-06-10T12:22:25.920843Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.921191Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.921450Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.921886Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech2\wpfjbb_revslider_layer_animations_bkp.ibd' OS error: 103
2025-06-10T12:22:25.922335Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.922612Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.923055Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech2/wpfjbb_revslider_layer_animations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.923689Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech2/wpfjbb_revslider_layer_animations_bkp` because it could not be opened.
2025-06-10T12:22:25.924337Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.924637Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.925181Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.925605Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech2\wpfjbb_revslider_navigations.ibd' OS error: 103
2025-06-10T12:22:25.926010Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.926279Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.926697Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech2/wpfjbb_revslider_navigations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.927375Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech2/wpfjbb_revslider_navigations` because it could not be opened.
2025-06-10T12:22:25.927837Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.928187Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.928568Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.929016Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech2\wpfjbb_revslider_navigations_bkp.ibd' OS error: 103
2025-06-10T12:22:25.929390Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.929747Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.930408Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech2/wpfjbb_revslider_navigations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.931123Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech2/wpfjbb_revslider_navigations_bkp` because it could not be opened.
2025-06-10T12:22:25.931624Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.932104Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.932632Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.933078Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech2\wpfjbb_revslider_sliders.ibd' OS error: 103
2025-06-10T12:22:25.933449Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.933718Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.934302Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech2/wpfjbb_revslider_sliders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.935117Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech2/wpfjbb_revslider_sliders` because it could not be opened.
2025-06-10T12:22:25.935661Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.935973Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.936290Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.936685Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech2\wpfjbb_revslider_sliders_bkp.ibd' OS error: 103
2025-06-10T12:22:25.937152Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.937514Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.937966Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech2/wpfjbb_revslider_sliders_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.938887Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech2/wpfjbb_revslider_sliders_bkp` because it could not be opened.
2025-06-10T12:22:25.939560Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.940000Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.940296Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.940678Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech2\wpfjbb_revslider_slides.ibd' OS error: 103
2025-06-10T12:22:25.941154Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.941425Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.941825Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech2/wpfjbb_revslider_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.942456Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech2/wpfjbb_revslider_slides` because it could not be opened.
2025-06-10T12:22:25.942893Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.943273Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.943571Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.943990Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech2\wpfjbb_revslider_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:25.944391Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.944649Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.945121Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech2/wpfjbb_revslider_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.945783Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech2/wpfjbb_revslider_slides_bkp` because it could not be opened.
2025-06-10T12:22:25.946619Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.946886Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.947249Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.947617Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech2\wpfjbb_revslider_static_slides.ibd' OS error: 103
2025-06-10T12:22:25.948042Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.948347Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.948750Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech2/wpfjbb_revslider_static_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.949467Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech2/wpfjbb_revslider_static_slides` because it could not be opened.
2025-06-10T12:22:25.949904Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.950305Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.950605Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.951144Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech2\wpfjbb_revslider_static_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:25.951663Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.951909Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.952488Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech2/wpfjbb_revslider_static_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.953247Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech2/wpfjbb_revslider_static_slides_bkp` because it could not be opened.
2025-06-10T12:22:25.953748Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.954185Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.954608Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.955117Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech2\wpfjbb_term_relationships.ibd' OS error: 103
2025-06-10T12:22:25.955505Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.955760Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.956251Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech2/wpfjbb_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.956833Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech2/wpfjbb_term_relationships` because it could not be opened.
2025-06-10T12:22:25.957413Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.957703Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.958160Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.958802Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech2\wpfjbb_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:25.959332Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.959625Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.960281Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech2/wpfjbb_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.960871Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech2/wpfjbb_term_taxonomy` because it could not be opened.
2025-06-10T12:22:25.961454Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.961830Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.962204Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.962571Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech2\wpfjbb_termmeta.ibd' OS error: 103
2025-06-10T12:22:25.963288Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.963601Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.964517Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech2/wpfjbb_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.965166Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech2/wpfjbb_termmeta` because it could not be opened.
2025-06-10T12:22:25.965683Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.966066Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.966360Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.966855Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech2\wpfjbb_terms.ibd' OS error: 103
2025-06-10T12:22:25.967282Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.967591Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.968483Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech2/wpfjbb_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.969477Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech2/wpfjbb_terms` because it could not be opened.
2025-06-10T12:22:25.970612Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.971255Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.971880Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.972665Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech2\wpfjbb_usermeta.ibd' OS error: 103
2025-06-10T12:22:25.973269Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.973768Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.974210Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech2/wpfjbb_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.974832Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech2/wpfjbb_usermeta` because it could not be opened.
2025-06-10T12:22:25.975257Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.975530Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.975993Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.976405Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_pentech2\wpfjbb_users.ibd' OS error: 103
2025-06-10T12:22:25.976808Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.977067Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.977468Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_pentech2/wpfjbb_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.978158Z 0 [Warning] InnoDB: Ignoring tablespace `client_pentech2/wpfjbb_users` because it could not be opened.
2025-06-10T12:22:25.978802Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.979089Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.979422Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.979898Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_actionscheduler_actions.ibd' OS error: 103
2025-06-10T12:22:25.980254Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.980503Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.981043Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_actionscheduler_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.981874Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_actionscheduler_actions` because it could not be opened.
2025-06-10T12:22:25.982465Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.982907Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.983175Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.983571Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_actionscheduler_claims.ibd' OS error: 103
2025-06-10T12:22:25.984118Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.984403Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.984841Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_actionscheduler_claims`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.985451Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_actionscheduler_claims` because it could not be opened.
2025-06-10T12:22:25.985980Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.986254Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.986532Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.986947Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_actionscheduler_groups.ibd' OS error: 103
2025-06-10T12:22:25.987317Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.987576Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.988018Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_actionscheduler_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.988659Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_actionscheduler_groups` because it could not be opened.
2025-06-10T12:22:25.989151Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.989507Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.989829Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.990220Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_actionscheduler_logs.ibd' OS error: 103
2025-06-10T12:22:25.990592Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.990895Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.991317Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_actionscheduler_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.992075Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_actionscheduler_logs` because it could not be opened.
2025-06-10T12:22:25.992653Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.993141Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.993476Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.994773Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_chaty_contact_form_leads.ibd' OS error: 103
2025-06-10T12:22:25.995301Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.995585Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:25.996059Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_chaty_contact_form_leads`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:25.997025Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_chaty_contact_form_leads` because it could not be opened.
2025-06-10T12:22:25.997916Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:25.998357Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:25.998691Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:25.999155Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:25.999580Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:25.999900Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.000394Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.001024Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:26.001514Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.001847Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.002223Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.002597Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_comments.ibd' OS error: 103
2025-06-10T12:22:26.002938Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.003291Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.003782Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.004491Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_comments` because it could not be opened.
2025-06-10T12:22:26.004998Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.005332Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.005594Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.006018Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:26.006485Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.006764Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.007235Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.007769Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_fbv` because it could not be opened.
2025-06-10T12:22:26.008508Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.008769Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.009120Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.009485Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:26.009826Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.010255Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.010655Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.011330Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:26.011750Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.012195Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.012561Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.013017Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_itsec_bans.ibd' OS error: 103
2025-06-10T12:22:26.013485Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.013764Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.014462Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_itsec_bans`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.015404Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_itsec_bans` because it could not be opened.
2025-06-10T12:22:26.015824Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.016193Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.016459Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.016824Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_itsec_dashboard_events.ibd' OS error: 103
2025-06-10T12:22:26.017247Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.017497Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.017953Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_itsec_dashboard_events`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.018984Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_itsec_dashboard_events` because it could not be opened.
2025-06-10T12:22:26.019693Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.020211Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.020602Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.021190Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_itsec_distributed_storage.ibd' OS error: 103
2025-06-10T12:22:26.021547Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.021795Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.022339Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_itsec_distributed_storage`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.023037Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_itsec_distributed_storage` because it could not be opened.
2025-06-10T12:22:26.023498Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.023938Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.024227Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.024696Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_itsec_fingerprints.ibd' OS error: 103
2025-06-10T12:22:26.025097Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.025377Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.025893Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_itsec_fingerprints`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.026519Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_itsec_fingerprints` because it could not be opened.
2025-06-10T12:22:26.027055Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.027344Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.027609Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.028118Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_itsec_geolocation_cache.ibd' OS error: 103
2025-06-10T12:22:26.028634Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.029043Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.029507Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_itsec_geolocation_cache`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.030229Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_itsec_geolocation_cache` because it could not be opened.
2025-06-10T12:22:26.030911Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.031202Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.031550Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.032022Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_itsec_lockouts.ibd' OS error: 103
2025-06-10T12:22:26.032378Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.032642Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.033110Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_itsec_lockouts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.033675Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_itsec_lockouts` because it could not be opened.
2025-06-10T12:22:26.034403Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.034686Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.035051Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.035678Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_itsec_logs.ibd' OS error: 103
2025-06-10T12:22:26.036257Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.036938Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.037895Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_itsec_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.038689Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_itsec_logs` because it could not be opened.
2025-06-10T12:22:26.039166Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.039556Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.039887Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.040289Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_itsec_mutexes.ibd' OS error: 103
2025-06-10T12:22:26.041013Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.041504Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.042007Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_itsec_mutexes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.043317Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_itsec_mutexes` because it could not be opened.
2025-06-10T12:22:26.043847Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.044130Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.044451Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.045035Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_itsec_opaque_tokens.ibd' OS error: 103
2025-06-10T12:22:26.045502Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.045773Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.046419Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_itsec_opaque_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.047110Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_itsec_opaque_tokens` because it could not be opened.
2025-06-10T12:22:26.047704Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.047985Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.048282Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.048792Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_itsec_temp.ibd' OS error: 103
2025-06-10T12:22:26.049156Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.049499Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.050016Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_itsec_temp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.050781Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_itsec_temp` because it could not be opened.
2025-06-10T12:22:26.051637Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.051990Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.052280Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.052802Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_itsec_user_groups.ibd' OS error: 103
2025-06-10T12:22:26.053181Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.053557Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.054011Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_itsec_user_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.054767Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_itsec_user_groups` because it could not be opened.
2025-06-10T12:22:26.055237Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.055569Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.055843Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.056228Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_links.ibd' OS error: 103
2025-06-10T12:22:26.056624Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.056889Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.057345Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.057920Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_links` because it could not be opened.
2025-06-10T12:22:26.058369Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.058643Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.058940Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.059392Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_options.ibd' OS error: 103
2025-06-10T12:22:26.059744Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.060013Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.060480Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.061066Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_options` because it could not be opened.
2025-06-10T12:22:26.061548Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.061829Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.062105Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.062525Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_post_views.ibd' OS error: 103
2025-06-10T12:22:26.062869Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.063132Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.063578Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_post_views`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.064162Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_post_views` because it could not be opened.
2025-06-10T12:22:26.064603Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.064872Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.065197Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.065651Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:26.065983Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.066240Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.066746Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.067365Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_postmeta` because it could not be opened.
2025-06-10T12:22:26.067817Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.068087Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.068405Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.068792Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_posts.ibd' OS error: 103
2025-06-10T12:22:26.069134Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.069491Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.069918Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.070534Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_posts` because it could not be opened.
2025-06-10T12:22:26.070949Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.071220Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.071556Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.071976Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:26.072377Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.072667Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.073369Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.074908Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:26.075396Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.075692Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.076065Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.076456Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:26.076808Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.077151Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.077566Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.078223Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:26.078690Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.079032Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.079298Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.079752Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:26.080191Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.080449Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.080921Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.081512Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_termmeta` because it could not be opened.
2025-06-10T12:22:26.082076Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.082443Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.082723Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.083231Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_terms.ibd' OS error: 103
2025-06-10T12:22:26.083665Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.083992Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.084496Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.085143Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_terms` because it could not be opened.
2025-06-10T12:22:26.085638Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.085934Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.086209Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.086593Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:26.086967Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.087416Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.087889Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.088595Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_usermeta` because it could not be opened.
2025-06-10T12:22:26.089059Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.089418Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.089694Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.090132Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_users.ibd' OS error: 103
2025-06-10T12:22:26.090463Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.090726Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.091181Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.091743Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_users` because it could not be opened.
2025-06-10T12:22:26.092278Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.092553Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.092857Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.093278Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_wc_admin_note_actions.ibd' OS error: 103
2025-06-10T12:22:26.093960Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.094235Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.094655Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_wc_admin_note_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.095289Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_wc_admin_note_actions` because it could not be opened.
2025-06-10T12:22:26.095731Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.096036Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.096358Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.096785Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_wc_admin_notes.ibd' OS error: 103
2025-06-10T12:22:26.097167Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.097434Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.098046Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_wc_admin_notes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.098984Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_wc_admin_notes` because it could not be opened.
2025-06-10T12:22:26.099567Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.099861Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.100683Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.101515Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_wc_category_lookup.ibd' OS error: 103
2025-06-10T12:22:26.102184Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.102535Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.103074Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_wc_category_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.103794Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_wc_category_lookup` because it could not be opened.
2025-06-10T12:22:26.104457Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.104739Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.105556Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.106178Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_wc_customer_lookup.ibd' OS error: 103
2025-06-10T12:22:26.106807Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.107245Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.107829Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_wc_customer_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.108752Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_wc_customer_lookup` because it could not be opened.
2025-06-10T12:22:26.109546Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.109965Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.110391Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.111070Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_wc_download_log.ibd' OS error: 103
2025-06-10T12:22:26.111489Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.111825Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.112302Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_wc_download_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.113034Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_wc_download_log` because it could not be opened.
2025-06-10T12:22:26.113634Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.114604Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.114957Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.115365Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_wc_order_coupon_lookup.ibd' OS error: 103
2025-06-10T12:22:26.115738Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.116039Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.116462Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_wc_order_coupon_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.117110Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_wc_order_coupon_lookup` because it could not be opened.
2025-06-10T12:22:26.117951Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.118408Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.118885Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.119932Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_wc_order_product_lookup.ibd' OS error: 103
2025-06-10T12:22:26.120477Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.120818Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.121544Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_wc_order_product_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.123323Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_wc_order_product_lookup` because it could not be opened.
2025-06-10T12:22:26.124112Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.124532Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.125017Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.126430Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_wc_order_stats.ibd' OS error: 103
2025-06-10T12:22:26.127199Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.127629Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.128355Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_wc_order_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.128993Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_wc_order_stats` because it could not be opened.
2025-06-10T12:22:26.129440Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.129714Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.130032Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.130475Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_wc_order_tax_lookup.ibd' OS error: 103
2025-06-10T12:22:26.130928Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.131443Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.131915Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_wc_order_tax_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.132695Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_wc_order_tax_lookup` because it could not be opened.
2025-06-10T12:22:26.133233Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.133546Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.133849Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.134293Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_wc_product_meta_lookup.ibd' OS error: 103
2025-06-10T12:22:26.134765Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.135116Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.135549Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_wc_product_meta_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.136217Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_wc_product_meta_lookup` because it could not be opened.
2025-06-10T12:22:26.136798Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.137205Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.137480Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.138566Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_wc_reserved_stock.ibd' OS error: 103
2025-06-10T12:22:26.139197Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.139488Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.139926Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_wc_reserved_stock`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.140770Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_wc_reserved_stock` because it could not be opened.
2025-06-10T12:22:26.141255Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.141727Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.142304Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.142833Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_wc_tax_rate_classes.ibd' OS error: 103
2025-06-10T12:22:26.143373Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.144166Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.144750Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_wc_tax_rate_classes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.146161Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_wc_tax_rate_classes` because it could not be opened.
2025-06-10T12:22:26.147680Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.148288Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.148968Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.149398Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_wc_webhooks.ibd' OS error: 103
2025-06-10T12:22:26.149976Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.150586Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.151237Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_wc_webhooks`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.151936Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_wc_webhooks` because it could not be opened.
2025-06-10T12:22:26.153926Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.154388Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.154897Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.156002Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_woocommerce_api_keys.ibd' OS error: 103
2025-06-10T12:22:26.156582Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.157059Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.157615Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_woocommerce_api_keys`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.158615Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_woocommerce_api_keys` because it could not be opened.
2025-06-10T12:22:26.159593Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.160041Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.160522Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.161214Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_woocommerce_attribute_taxonomies.ibd' OS error: 103
2025-06-10T12:22:26.161953Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.162285Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.163334Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_woocommerce_attribute_taxonomies`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.166009Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_woocommerce_attribute_taxonomies` because it could not be opened.
2025-06-10T12:22:26.166630Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.166985Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.167969Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.168876Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_woocommerce_downloadable_product_permissions.ibd' OS error: 103
2025-06-10T12:22:26.169397Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.169844Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.170540Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_woocommerce_downloadable_product_permissions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.171984Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_woocommerce_downloadable_product_permissions` because it could not be opened.
2025-06-10T12:22:26.172739Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.173205Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.173628Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.174715Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_woocommerce_log.ibd' OS error: 103
2025-06-10T12:22:26.175877Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.178319Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.179373Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_woocommerce_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.180335Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_woocommerce_log` because it could not be opened.
2025-06-10T12:22:26.181463Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.182007Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.182309Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.182824Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_woocommerce_order_itemmeta.ibd' OS error: 103
2025-06-10T12:22:26.183416Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.183756Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.184426Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_woocommerce_order_itemmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.185509Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_woocommerce_order_itemmeta` because it could not be opened.
2025-06-10T12:22:26.186463Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.187061Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.187738Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.188590Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_woocommerce_order_items.ibd' OS error: 103
2025-06-10T12:22:26.189181Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.189500Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.190041Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_woocommerce_order_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.190684Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_woocommerce_order_items` because it could not be opened.
2025-06-10T12:22:26.191178Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.191454Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.191775Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.192352Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_woocommerce_payment_tokenmeta.ibd' OS error: 103
2025-06-10T12:22:26.193864Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.194220Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.195121Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_woocommerce_payment_tokenmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.195958Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_woocommerce_payment_tokenmeta` because it could not be opened.
2025-06-10T12:22:26.196542Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.196992Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.197648Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.198458Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_woocommerce_payment_tokens.ibd' OS error: 103
2025-06-10T12:22:26.198884Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.199174Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.199619Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_woocommerce_payment_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.200498Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_woocommerce_payment_tokens` because it could not be opened.
2025-06-10T12:22:26.201708Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.202233Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.202545Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.202955Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_woocommerce_sessions.ibd' OS error: 103
2025-06-10T12:22:26.203345Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.203744Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.204875Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_woocommerce_sessions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.206293Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_woocommerce_sessions` because it could not be opened.
2025-06-10T12:22:26.206974Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.207654Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.208408Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.209419Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_woocommerce_shipping_zone_locations.ibd' OS error: 103
2025-06-10T12:22:26.210303Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.211036Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.211610Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_woocommerce_shipping_zone_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.212394Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_woocommerce_shipping_zone_locations` because it could not be opened.
2025-06-10T12:22:26.212984Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.213328Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.213777Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.214208Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_woocommerce_shipping_zone_methods.ibd' OS error: 103
2025-06-10T12:22:26.214608Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.215048Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.215765Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_woocommerce_shipping_zone_methods`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.216847Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_woocommerce_shipping_zone_methods` because it could not be opened.
2025-06-10T12:22:26.217500Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.218092Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.218554Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.219237Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_woocommerce_shipping_zones.ibd' OS error: 103
2025-06-10T12:22:26.219808Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.220204Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.220809Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_woocommerce_shipping_zones`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.221601Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_woocommerce_shipping_zones` because it could not be opened.
2025-06-10T12:22:26.222146Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.222543Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.223055Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.223550Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_woocommerce_tax_rate_locations.ibd' OS error: 103
2025-06-10T12:22:26.224064Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.224517Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.225155Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_woocommerce_tax_rate_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.226096Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_woocommerce_tax_rate_locations` because it could not be opened.
2025-06-10T12:22:26.226754Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.227212Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.227682Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.228229Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_woocommerce_tax_rates.ibd' OS error: 103
2025-06-10T12:22:26.228712Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.228996Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.229645Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_woocommerce_tax_rates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.230389Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_woocommerce_tax_rates` because it could not be opened.
2025-06-10T12:22:26.230916Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.231249Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.231538Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.231959Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:26.232323Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.232634Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.233091Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.233740Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:26.234345Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.234911Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.235237Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.235681Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:26.236132Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.236518Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.236990Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.237682Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:26.238223Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.238593Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.238896Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.239335Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:26.239722Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.240003Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.240452Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.241079Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:26.241508Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.241847Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.242332Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.242796Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_prosolution1\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:26.243217Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.243523Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.244246Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_prosolution1/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.245167Z 0 [Warning] InnoDB: Ignoring tablespace `client_prosolution1/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:26.245996Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.246393Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.246731Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.247138Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_rocc1\wp_actionscheduler_actions.ibd' OS error: 103
2025-06-10T12:22:26.247529Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.248207Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.249362Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_rocc1/wp_actionscheduler_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.250422Z 0 [Warning] InnoDB: Ignoring tablespace `client_rocc1/wp_actionscheduler_actions` because it could not be opened.
2025-06-10T12:22:26.251686Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.252127Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.252530Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.253011Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_rocc1\wp_actionscheduler_claims.ibd' OS error: 103
2025-06-10T12:22:26.253679Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.254129Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.254760Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_rocc1/wp_actionscheduler_claims`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.256116Z 0 [Warning] InnoDB: Ignoring tablespace `client_rocc1/wp_actionscheduler_claims` because it could not be opened.
2025-06-10T12:22:26.256942Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.257598Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.259427Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.260388Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_rocc1\wp_actionscheduler_groups.ibd' OS error: 103
2025-06-10T12:22:26.260848Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.261139Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.261583Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_rocc1/wp_actionscheduler_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.262315Z 0 [Warning] InnoDB: Ignoring tablespace `client_rocc1/wp_actionscheduler_groups` because it could not be opened.
2025-06-10T12:22:26.262985Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.263282Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.263559Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.264051Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_rocc1\wp_actionscheduler_logs.ibd' OS error: 103
2025-06-10T12:22:26.264398Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.264719Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.265162Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_rocc1/wp_actionscheduler_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.265801Z 0 [Warning] InnoDB: Ignoring tablespace `client_rocc1/wp_actionscheduler_logs` because it could not be opened.
2025-06-10T12:22:26.266235Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.266505Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.266808Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.267187Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_rocc1\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:26.267516Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.267851Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.268266Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_rocc1/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.268859Z 0 [Warning] InnoDB: Ignoring tablespace `client_rocc1/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:26.269233Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.269499Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.269809Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.270172Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_rocc1\wp_comments.ibd' OS error: 103
2025-06-10T12:22:26.270477Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.270795Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.271250Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_rocc1/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.271953Z 0 [Warning] InnoDB: Ignoring tablespace `client_rocc1/wp_comments` because it could not be opened.
2025-06-10T12:22:26.272381Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.272663Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.272952Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.273336Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_rocc1\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:26.273784Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.274096Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.274522Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_rocc1/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.275101Z 0 [Warning] InnoDB: Ignoring tablespace `client_rocc1/wp_fbv` because it could not be opened.
2025-06-10T12:22:26.275533Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.275852Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.276156Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.276591Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_rocc1\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:26.277100Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.277372Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.277964Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_rocc1/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.278909Z 0 [Warning] InnoDB: Ignoring tablespace `client_rocc1/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:26.279491Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.279822Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.280084Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.280450Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_rocc1\wp_links.ibd' OS error: 103
2025-06-10T12:22:26.280835Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.281161Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.281621Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_rocc1/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.282749Z 0 [Warning] InnoDB: Ignoring tablespace `client_rocc1/wp_links` because it could not be opened.
2025-06-10T12:22:26.283274Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.283542Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.284087Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.284479Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_rocc1\wp_options.ibd' OS error: 103
2025-06-10T12:22:26.284907Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.285260Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.285737Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_rocc1/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.286604Z 0 [Warning] InnoDB: Ignoring tablespace `client_rocc1/wp_options` because it could not be opened.
2025-06-10T12:22:26.287252Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.287670Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.287955Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.288347Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_rocc1\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:26.288703Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.288975Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.289496Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_rocc1/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.290217Z 0 [Warning] InnoDB: Ignoring tablespace `client_rocc1/wp_postmeta` because it could not be opened.
2025-06-10T12:22:26.290764Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.291062Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.291345Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.291859Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_rocc1\wp_posts.ibd' OS error: 103
2025-06-10T12:22:26.292188Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.292476Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.292965Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_rocc1/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.293524Z 0 [Warning] InnoDB: Ignoring tablespace `client_rocc1/wp_posts` because it could not be opened.
2025-06-10T12:22:26.293957Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.294226Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.294498Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.294930Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_rocc1\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:26.295283Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.295556Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.296028Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_rocc1/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.296661Z 0 [Warning] InnoDB: Ignoring tablespace `client_rocc1/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:26.297151Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.297421Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.297727Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.298112Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_rocc1\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:26.298449Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.298750Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.299161Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_rocc1/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.299774Z 0 [Warning] InnoDB: Ignoring tablespace `client_rocc1/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:26.300181Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.300509Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.300829Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.301204Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_rocc1\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:26.301519Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.301831Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.302287Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_rocc1/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.302932Z 0 [Warning] InnoDB: Ignoring tablespace `client_rocc1/wp_termmeta` because it could not be opened.
2025-06-10T12:22:26.303317Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.303617Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.303898Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.304276Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_rocc1\wp_terms.ibd' OS error: 103
2025-06-10T12:22:26.304655Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.304921Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.305341Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_rocc1/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.306000Z 0 [Warning] InnoDB: Ignoring tablespace `client_rocc1/wp_terms` because it could not be opened.
2025-06-10T12:22:26.306506Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.306848Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.307127Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.307520Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_rocc1\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:26.307874Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.308137Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.308594Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_rocc1/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.309172Z 0 [Warning] InnoDB: Ignoring tablespace `client_rocc1/wp_usermeta` because it could not be opened.
2025-06-10T12:22:26.309601Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.309876Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.310180Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.310619Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_rocc1\wp_users.ibd' OS error: 103
2025-06-10T12:22:26.310937Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.311251Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.311714Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_rocc1/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.312752Z 0 [Warning] InnoDB: Ignoring tablespace `client_rocc1/wp_users` because it could not be opened.
2025-06-10T12:22:26.313194Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.313517Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.313908Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.314313Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_rocc1\wp_wc_admin_note_actions.ibd' OS error: 103
2025-06-10T12:22:26.314760Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.315088Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.315499Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_rocc1/wp_wc_admin_note_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.316185Z 0 [Warning] InnoDB: Ignoring tablespace `client_rocc1/wp_wc_admin_note_actions` because it could not be opened.
2025-06-10T12:22:26.316693Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.316975Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.317249Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.317703Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_rocc1\wp_wc_admin_notes.ibd' OS error: 103
2025-06-10T12:22:26.318045Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.318310Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.318824Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_rocc1/wp_wc_admin_notes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.319407Z 0 [Warning] InnoDB: Ignoring tablespace `client_rocc1/wp_wc_admin_notes` because it could not be opened.
2025-06-10T12:22:26.319928Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.320195Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.320474Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.320942Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_rocc1\wp_wc_category_lookup.ibd' OS error: 103
2025-06-10T12:22:26.321297Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.321650Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.322163Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_rocc1/wp_wc_category_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.322795Z 0 [Warning] InnoDB: Ignoring tablespace `client_rocc1/wp_wc_category_lookup` because it could not be opened.
2025-06-10T12:22:26.323202Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.323461Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.323810Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.324235Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_rocc1\wp_wc_customer_lookup.ibd' OS error: 103
2025-06-10T12:22:26.324633Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.324911Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.325334Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_rocc1/wp_wc_customer_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.325991Z 0 [Warning] InnoDB: Ignoring tablespace `client_rocc1/wp_wc_customer_lookup` because it could not be opened.
2025-06-10T12:22:26.326434Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.326728Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.327003Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.327397Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_rocc1\wp_wc_download_log.ibd' OS error: 103
2025-06-10T12:22:26.327781Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.328046Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.328478Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_rocc1/wp_wc_download_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.329082Z 0 [Warning] InnoDB: Ignoring tablespace `client_rocc1/wp_wc_download_log` because it could not be opened.
2025-06-10T12:22:26.329492Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.329790Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.330066Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.330449Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_rocc1\wp_wc_order_coupon_lookup.ibd' OS error: 103
2025-06-10T12:22:26.330925Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.331213Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.331665Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_rocc1/wp_wc_order_coupon_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.332264Z 0 [Warning] InnoDB: Ignoring tablespace `client_rocc1/wp_wc_order_coupon_lookup` because it could not be opened.
2025-06-10T12:22:26.332796Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.333050Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.333307Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.333753Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_rocc1\wp_wc_order_product_lookup.ibd' OS error: 103
2025-06-10T12:22:26.334092Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.334342Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.334818Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_rocc1/wp_wc_order_product_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.335375Z 0 [Warning] InnoDB: Ignoring tablespace `client_rocc1/wp_wc_order_product_lookup` because it could not be opened.
2025-06-10T12:22:26.336082Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.336345Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.336654Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.337019Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_rocc1\wp_wc_order_stats.ibd' OS error: 103
2025-06-10T12:22:26.337339Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.337680Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.338113Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_rocc1/wp_wc_order_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.338763Z 0 [Warning] InnoDB: Ignoring tablespace `client_rocc1/wp_wc_order_stats` because it could not be opened.
2025-06-10T12:22:26.339143Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.339394Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.339745Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.340137Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_rocc1\wp_wc_order_tax_lookup.ibd' OS error: 103
2025-06-10T12:22:26.340705Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.340961Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.341359Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_rocc1/wp_wc_order_tax_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.342094Z 0 [Warning] InnoDB: Ignoring tablespace `client_rocc1/wp_wc_order_tax_lookup` because it could not be opened.
2025-06-10T12:22:26.342782Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.343067Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.343467Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.344196Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_rocc1\wp_wc_product_meta_lookup.ibd' OS error: 103
2025-06-10T12:22:26.345290Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.345565Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.346356Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_rocc1/wp_wc_product_meta_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.347076Z 0 [Warning] InnoDB: Ignoring tablespace `client_rocc1/wp_wc_product_meta_lookup` because it could not be opened.
2025-06-10T12:22:26.347540Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.347871Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.348142Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.348527Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_rocc1\wp_wc_rate_limits.ibd' OS error: 103
2025-06-10T12:22:26.348929Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.349206Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.349674Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_rocc1/wp_wc_rate_limits`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.350291Z 0 [Warning] InnoDB: Ignoring tablespace `client_rocc1/wp_wc_rate_limits` because it could not be opened.
2025-06-10T12:22:26.350832Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.351118Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.351397Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.351876Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_rocc1\wp_wc_reserved_stock.ibd' OS error: 103
2025-06-10T12:22:26.352234Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.352887Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.353388Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_rocc1/wp_wc_reserved_stock`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.354098Z 0 [Warning] InnoDB: Ignoring tablespace `client_rocc1/wp_wc_reserved_stock` because it could not be opened.
2025-06-10T12:22:26.354553Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.354857Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.355132Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.355518Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_rocc1\wp_wc_tax_rate_classes.ibd' OS error: 103
2025-06-10T12:22:26.355893Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.356155Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.356564Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_rocc1/wp_wc_tax_rate_classes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.357249Z 0 [Warning] InnoDB: Ignoring tablespace `client_rocc1/wp_wc_tax_rate_classes` because it could not be opened.
2025-06-10T12:22:26.357753Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.358069Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.358346Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.358769Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_rocc1\wp_wc_webhooks.ibd' OS error: 103
2025-06-10T12:22:26.359187Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.359485Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.359940Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_rocc1/wp_wc_webhooks`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.360555Z 0 [Warning] InnoDB: Ignoring tablespace `client_rocc1/wp_wc_webhooks` because it could not be opened.
2025-06-10T12:22:26.361072Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.361365Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.361693Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.362085Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_rocc1\wp_woocommerce_api_keys.ibd' OS error: 103
2025-06-10T12:22:26.362431Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.362734Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.363152Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_rocc1/wp_woocommerce_api_keys`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.363771Z 0 [Warning] InnoDB: Ignoring tablespace `client_rocc1/wp_woocommerce_api_keys` because it could not be opened.
2025-06-10T12:22:26.364182Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.364518Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.364901Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.365499Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_rocc1\wp_woocommerce_attribute_taxonomies.ibd' OS error: 103
2025-06-10T12:22:26.365954Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.366222Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.366711Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_rocc1/wp_woocommerce_attribute_taxonomies`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.367321Z 0 [Warning] InnoDB: Ignoring tablespace `client_rocc1/wp_woocommerce_attribute_taxonomies` because it could not be opened.
2025-06-10T12:22:26.367855Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.368124Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.368394Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.368846Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_rocc1\wp_woocommerce_downloadable_product_permissions.ibd' OS error: 103
2025-06-10T12:22:26.369247Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.369508Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.369995Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_rocc1/wp_woocommerce_downloadable_product_permissions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.370687Z 0 [Warning] InnoDB: Ignoring tablespace `client_rocc1/wp_woocommerce_downloadable_product_permissions` because it could not be opened.
2025-06-10T12:22:26.371160Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.371475Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.371800Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.372183Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_rocc1\wp_woocommerce_log.ibd' OS error: 103
2025-06-10T12:22:26.372523Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.372858Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.373269Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_rocc1/wp_woocommerce_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.373918Z 0 [Warning] InnoDB: Ignoring tablespace `client_rocc1/wp_woocommerce_log` because it could not be opened.
2025-06-10T12:22:26.374332Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.374649Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.374922Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.375289Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_rocc1\wp_woocommerce_order_itemmeta.ibd' OS error: 103
2025-06-10T12:22:26.375807Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.376126Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.376587Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_rocc1/wp_woocommerce_order_itemmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.377285Z 0 [Warning] InnoDB: Ignoring tablespace `client_rocc1/wp_woocommerce_order_itemmeta` because it could not be opened.
2025-06-10T12:22:26.378501Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.378773Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.379048Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.379503Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_rocc1\wp_woocommerce_order_items.ibd' OS error: 103
2025-06-10T12:22:26.379862Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.380123Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.380604Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_rocc1/wp_woocommerce_order_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.381202Z 0 [Warning] InnoDB: Ignoring tablespace `client_rocc1/wp_woocommerce_order_items` because it could not be opened.
2025-06-10T12:22:26.381747Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.382018Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.382286Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.382748Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_rocc1\wp_woocommerce_payment_tokenmeta.ibd' OS error: 103
2025-06-10T12:22:26.383119Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.383464Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.383882Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_rocc1/wp_woocommerce_payment_tokenmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.384619Z 0 [Warning] InnoDB: Ignoring tablespace `client_rocc1/wp_woocommerce_payment_tokenmeta` because it could not be opened.
2025-06-10T12:22:26.385185Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.385494Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.385776Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.386165Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_rocc1\wp_woocommerce_payment_tokens.ibd' OS error: 103
2025-06-10T12:22:26.386563Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.386827Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.387241Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_rocc1/wp_woocommerce_payment_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.387947Z 0 [Warning] InnoDB: Ignoring tablespace `client_rocc1/wp_woocommerce_payment_tokens` because it could not be opened.
2025-06-10T12:22:26.388457Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.388734Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.389013Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.389444Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_rocc1\wp_woocommerce_sessions.ibd' OS error: 103
2025-06-10T12:22:26.389793Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.390054Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.390517Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_rocc1/wp_woocommerce_sessions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.391246Z 0 [Warning] InnoDB: Ignoring tablespace `client_rocc1/wp_woocommerce_sessions` because it could not be opened.
2025-06-10T12:22:26.391769Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.392034Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.392345Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.392781Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_rocc1\wp_woocommerce_shipping_zone_locations.ibd' OS error: 103
2025-06-10T12:22:26.393184Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.393530Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.393942Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_rocc1/wp_woocommerce_shipping_zone_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.394607Z 0 [Warning] InnoDB: Ignoring tablespace `client_rocc1/wp_woocommerce_shipping_zone_locations` because it could not be opened.
2025-06-10T12:22:26.395169Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.395468Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.395747Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.396134Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_rocc1\wp_woocommerce_shipping_zone_methods.ibd' OS error: 103
2025-06-10T12:22:26.396606Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.396873Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.397384Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_rocc1/wp_woocommerce_shipping_zone_methods`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.398169Z 0 [Warning] InnoDB: Ignoring tablespace `client_rocc1/wp_woocommerce_shipping_zone_methods` because it could not be opened.
2025-06-10T12:22:26.398842Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.399126Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.399453Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.399847Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_rocc1\wp_woocommerce_shipping_zones.ibd' OS error: 103
2025-06-10T12:22:26.400216Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.400504Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.400926Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_rocc1/wp_woocommerce_shipping_zones`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.401586Z 0 [Warning] InnoDB: Ignoring tablespace `client_rocc1/wp_woocommerce_shipping_zones` because it could not be opened.
2025-06-10T12:22:26.402058Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.402366Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.402670Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.403063Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_rocc1\wp_woocommerce_tax_rate_locations.ibd' OS error: 103
2025-06-10T12:22:26.403465Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.403855Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.404352Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_rocc1/wp_woocommerce_tax_rate_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.404966Z 0 [Warning] InnoDB: Ignoring tablespace `client_rocc1/wp_woocommerce_tax_rate_locations` because it could not be opened.
2025-06-10T12:22:26.405544Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.405804Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.406062Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.406534Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_rocc1\wp_woocommerce_tax_rates.ibd' OS error: 103
2025-06-10T12:22:26.406910Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.407226Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.409393Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_rocc1/wp_woocommerce_tax_rates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.410019Z 0 [Warning] InnoDB: Ignoring tablespace `client_rocc1/wp_woocommerce_tax_rates` because it could not be opened.
2025-06-10T12:22:26.410592Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.410896Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.411183Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.411634Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_rocc1\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:26.412013Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.412315Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.412935Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_rocc1/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.413565Z 0 [Warning] InnoDB: Ignoring tablespace `client_rocc1/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:26.414039Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.414300Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.414644Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.415066Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_rocc1\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:26.415484Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.415825Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.416326Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_rocc1/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.416955Z 0 [Warning] InnoDB: Ignoring tablespace `client_rocc1/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:26.417424Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.417753Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.418046Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.418494Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_rocc1\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:26.418807Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.419061Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.419523Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_rocc1/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.420071Z 0 [Warning] InnoDB: Ignoring tablespace `client_rocc1/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:26.420519Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.420776Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.421037Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.421453Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_rocc1\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:26.421811Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.422064Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.422577Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_rocc1/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.423171Z 0 [Warning] InnoDB: Ignoring tablespace `client_rocc1/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:26.424006Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.424335Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.424652Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.425023Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_actionscheduler_actions.ibd' OS error: 103
2025-06-10T12:22:26.425411Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.425688Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.426217Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_actionscheduler_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.426879Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_actionscheduler_actions` because it could not be opened.
2025-06-10T12:22:26.427549Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.427821Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.428087Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.428519Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_actionscheduler_claims.ibd' OS error: 103
2025-06-10T12:22:26.428856Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.429107Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.429564Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_actionscheduler_claims`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.430126Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_actionscheduler_claims` because it could not be opened.
2025-06-10T12:22:26.430614Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.430868Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.431130Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.431598Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_actionscheduler_groups.ibd' OS error: 103
2025-06-10T12:22:26.431932Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.432183Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.432694Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_actionscheduler_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.433404Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_actionscheduler_groups` because it could not be opened.
2025-06-10T12:22:26.433897Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.434174Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.434524Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.434915Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_actionscheduler_logs.ibd' OS error: 103
2025-06-10T12:22:26.435267Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.435609Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.436062Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_actionscheduler_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.436778Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_actionscheduler_logs` because it could not be opened.
2025-06-10T12:22:26.437244Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.437652Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.438003Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.438477Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_canvas_notifications.ibd' OS error: 103
2025-06-10T12:22:26.438818Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.439090Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.439728Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_canvas_notifications`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.440509Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_canvas_notifications` because it could not be opened.
2025-06-10T12:22:26.441187Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.441549Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.441831Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.442370Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_cscs_db_subscriptions.ibd' OS error: 103
2025-06-10T12:22:26.442768Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.443035Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.443478Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_cscs_db_subscriptions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.444067Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_cscs_db_subscriptions` because it could not be opened.
2025-06-10T12:22:26.444536Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.445167Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.445475Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.445848Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:26.446235Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.446549Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.447309Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.448223Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_fbv` because it could not be opened.
2025-06-10T12:22:26.448845Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.449101Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.449532Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.449893Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:26.450348Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.450630Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.451025Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.451865Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:26.452680Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.452961Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.453267Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.453658Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_itsec_bans.ibd' OS error: 103
2025-06-10T12:22:26.453982Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.454321Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.454733Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_itsec_bans`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.455359Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_itsec_bans` because it could not be opened.
2025-06-10T12:22:26.455754Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.456050Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.456405Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.456785Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_itsec_distributed_storage.ibd' OS error: 103
2025-06-10T12:22:26.457259Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.457591Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.457978Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_itsec_distributed_storage`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.458755Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_itsec_distributed_storage` because it could not be opened.
2025-06-10T12:22:26.459288Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.459700Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.460044Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.460456Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_itsec_fingerprints.ibd' OS error: 103
2025-06-10T12:22:26.460782Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.461134Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.461663Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_itsec_fingerprints`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.462411Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_itsec_fingerprints` because it could not be opened.
2025-06-10T12:22:26.462859Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.463149Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.463431Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.463803Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_itsec_geolocation_cache.ibd' OS error: 103
2025-06-10T12:22:26.464197Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.464469Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.464891Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_itsec_geolocation_cache`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.465571Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_itsec_geolocation_cache` because it could not be opened.
2025-06-10T12:22:26.466012Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.466373Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.466686Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.467058Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_itsec_lockouts.ibd' OS error: 103
2025-06-10T12:22:26.467461Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.467739Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.468193Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_itsec_lockouts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.468760Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_itsec_lockouts` because it could not be opened.
2025-06-10T12:22:26.469251Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.469524Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.469785Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.470203Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_itsec_logs.ibd' OS error: 103
2025-06-10T12:22:26.470531Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.470781Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.471230Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_itsec_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.471927Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_itsec_logs` because it could not be opened.
2025-06-10T12:22:26.472367Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.472641Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.472916Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.473376Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_itsec_mutexes.ibd' OS error: 103
2025-06-10T12:22:26.473713Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.474170Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.474588Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_itsec_mutexes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.475235Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_itsec_mutexes` because it could not be opened.
2025-06-10T12:22:26.475701Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.475979Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.476335Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.476714Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_itsec_opaque_tokens.ibd' OS error: 103
2025-06-10T12:22:26.477054Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.477374Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.477837Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_itsec_opaque_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.478484Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_itsec_opaque_tokens` because it could not be opened.
2025-06-10T12:22:26.478881Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.479224Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.479505Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.479875Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_itsec_temp.ibd' OS error: 103
2025-06-10T12:22:26.480268Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.480525Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.480922Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_itsec_temp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.481530Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_itsec_temp` because it could not be opened.
2025-06-10T12:22:26.481968Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.482267Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.482595Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.483007Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_itsec_user_groups.ibd' OS error: 103
2025-06-10T12:22:26.483613Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.483877Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.484471Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_itsec_user_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.485277Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_itsec_user_groups` because it could not be opened.
2025-06-10T12:22:26.485844Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.486209Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.486478Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.486836Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_mclean_refs.ibd' OS error: 103
2025-06-10T12:22:26.487285Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.487575Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.487980Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_mclean_refs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.488738Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_mclean_refs` because it could not be opened.
2025-06-10T12:22:26.489690Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.490220Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.490551Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.491217Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_mclean_scan.ibd' OS error: 103
2025-06-10T12:22:26.491623Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.491981Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.492444Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_mclean_scan`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.493192Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_mclean_scan` because it could not be opened.
2025-06-10T12:22:26.493618Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.493873Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.494202Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.494566Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_pms_member_subscriptionmeta.ibd' OS error: 103
2025-06-10T12:22:26.494910Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.495250Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.495699Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_pms_member_subscriptionmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.496425Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_pms_member_subscriptionmeta` because it could not be opened.
2025-06-10T12:22:26.496901Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.497286Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.497562Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.498007Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_pms_member_subscriptions.ibd' OS error: 103
2025-06-10T12:22:26.498617Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.499051Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.499903Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_pms_member_subscriptions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.500676Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_pms_member_subscriptions` because it could not be opened.
2025-06-10T12:22:26.501194Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.501466Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.501741Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.502185Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_pms_paymentmeta.ibd' OS error: 103
2025-06-10T12:22:26.502525Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.502791Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.503277Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_pms_paymentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.503851Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_pms_paymentmeta` because it could not be opened.
2025-06-10T12:22:26.504340Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.504605Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.504878Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.505331Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_pms_payments.ibd' OS error: 103
2025-06-10T12:22:26.505665Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.505978Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.506505Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_pms_payments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.507164Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_pms_payments` because it could not be opened.
2025-06-10T12:22:26.507563Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.507822Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.508212Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.508634Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_sb_integrations.ibd' OS error: 103
2025-06-10T12:22:26.509087Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.509351Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.509768Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_sb_integrations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.510415Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_sb_integrations` because it could not be opened.
2025-06-10T12:22:26.510815Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.511142Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.511415Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.511795Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_socialbug_affiliates.ibd' OS error: 103
2025-06-10T12:22:26.512320Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.512595Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.513206Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_socialbug_affiliates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.514333Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_socialbug_affiliates` because it could not be opened.
2025-06-10T12:22:26.514827Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.515173Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.515474Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.515908Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_wc_admin_note_actions.ibd' OS error: 103
2025-06-10T12:22:26.516331Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.516647Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.517201Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_wc_admin_note_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.517948Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_wc_admin_note_actions` because it could not be opened.
2025-06-10T12:22:26.518446Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.518715Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.519059Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.519444Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_wc_admin_notes.ibd' OS error: 103
2025-06-10T12:22:26.519767Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.520146Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.520610Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_wc_admin_notes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.521260Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_wc_admin_notes` because it could not be opened.
2025-06-10T12:22:26.521720Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.522032Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.522308Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.522891Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_wc_category_lookup.ibd' OS error: 103
2025-06-10T12:22:26.523284Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.523546Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.524116Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_wc_category_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.524949Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_wc_category_lookup` because it could not be opened.
2025-06-10T12:22:26.525455Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.525792Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.526068Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.526627Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_wc_customer_lookup.ibd' OS error: 103
2025-06-10T12:22:26.527165Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.527432Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.527936Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_wc_customer_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.528604Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_wc_customer_lookup` because it could not be opened.
2025-06-10T12:22:26.529059Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.529342Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.529836Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.530322Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_wc_order_coupon_lookup.ibd' OS error: 103
2025-06-10T12:22:26.530902Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.531182Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.531650Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_wc_order_coupon_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.532286Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_wc_order_coupon_lookup` because it could not be opened.
2025-06-10T12:22:26.532837Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.533107Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.533381Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.533840Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_wc_order_product_lookup.ibd' OS error: 103
2025-06-10T12:22:26.534201Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.534466Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.534954Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_wc_order_product_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.535685Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_wc_order_product_lookup` because it could not be opened.
2025-06-10T12:22:26.536201Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.536506Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.536838Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.537234Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_wc_order_stats.ibd' OS error: 103
2025-06-10T12:22:26.537667Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.537945Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.538393Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_wc_order_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.539010Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_wc_order_stats` because it could not be opened.
2025-06-10T12:22:26.539558Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.539856Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.540141Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.540562Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_wc_order_tax_lookup.ibd' OS error: 103
2025-06-10T12:22:26.541067Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.541336Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.541779Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_wc_order_tax_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.542364Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_wc_order_tax_lookup` because it could not be opened.
2025-06-10T12:22:26.542809Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.543077Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.543349Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.543767Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_wc_reserved_stock.ibd' OS error: 103
2025-06-10T12:22:26.544107Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.544366Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.544809Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_wc_reserved_stock`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.545380Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_wc_reserved_stock` because it could not be opened.
2025-06-10T12:22:26.545814Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.546080Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.546352Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.546762Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_woo_ua_auction_log.ibd' OS error: 103
2025-06-10T12:22:26.547115Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.547374Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.547815Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_woo_ua_auction_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.548402Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_woo_ua_auction_log` because it could not be opened.
2025-06-10T12:22:26.548913Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.549187Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.549478Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.549881Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_wpam_actions.ibd' OS error: 103
2025-06-10T12:22:26.550208Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.550497Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.551159Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_wpam_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.552089Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_wpam_actions` because it could not be opened.
2025-06-10T12:22:26.552628Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.552965Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.553314Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.553769Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_wpam_affiliates.ibd' OS error: 103
2025-06-10T12:22:26.554168Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.554767Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.555265Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_wpam_affiliates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.556081Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_wpam_affiliates` because it could not be opened.
2025-06-10T12:22:26.556538Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.556858Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.557134Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.557523Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_wpam_affiliates_fields.ibd' OS error: 103
2025-06-10T12:22:26.557915Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.558184Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.558823Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_wpam_affiliates_fields`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.559471Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_wpam_affiliates_fields` because it could not be opened.
2025-06-10T12:22:26.560012Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.560277Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.560597Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.561074Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_wpam_creatives.ibd' OS error: 103
2025-06-10T12:22:26.561685Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.562188Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.562692Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_wpam_creatives`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.563415Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_wpam_creatives` because it could not be opened.
2025-06-10T12:22:26.563914Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.564164Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.564416Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.564893Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_wpam_events.ibd' OS error: 103
2025-06-10T12:22:26.565258Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.565692Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.566118Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_wpam_events`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.566815Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_wpam_events` because it could not be opened.
2025-06-10T12:22:26.567190Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.567437Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.567811Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.568165Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_wpam_impressions.ibd' OS error: 103
2025-06-10T12:22:26.568480Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.568810Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.569198Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_wpam_impressions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.569809Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_wpam_impressions` because it could not be opened.
2025-06-10T12:22:26.570169Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.570415Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.570752Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.571111Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_wpam_messages.ibd' OS error: 103
2025-06-10T12:22:26.571436Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.571834Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.572352Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_wpam_messages`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.572982Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_wpam_messages` because it could not be opened.
2025-06-10T12:22:26.573485Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.573895Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.574159Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.574709Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_wpam_paypal_logs.ibd' OS error: 103
2025-06-10T12:22:26.575071Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.575316Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.575946Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_wpam_paypal_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.576781Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_wpam_paypal_logs` because it could not be opened.
2025-06-10T12:22:26.577192Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.577441Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.577833Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.578218Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_wpam_tracking_tokens.ibd' OS error: 103
2025-06-10T12:22:26.578655Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.579065Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.579565Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_wpam_tracking_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.580208Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_wpam_tracking_tokens` because it could not be opened.
2025-06-10T12:22:26.580833Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.581143Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.581460Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.582009Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_wpam_tracking_tokens_purchase_logs.ibd' OS error: 103
2025-06-10T12:22:26.582386Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.582716Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.583135Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_wpam_tracking_tokens_purchase_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.583808Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_wpam_tracking_tokens_purchase_logs` because it could not be opened.
2025-06-10T12:22:26.584336Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.584666Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.584944Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.585411Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_wpam_transactions.ibd' OS error: 103
2025-06-10T12:22:26.586324Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.587104Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.587763Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_wpam_transactions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.588372Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_wpam_transactions` because it could not be opened.
2025-06-10T12:22:26.588840Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.589128Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.589404Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.589795Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_wpfm_backup.ibd' OS error: 103
2025-06-10T12:22:26.590179Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.590576Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.591015Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_wpfm_backup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.591775Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_wpfm_backup` because it could not be opened.
2025-06-10T12:22:26.592340Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.592622Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.592902Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.593326Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_yoast_indexable.ibd' OS error: 103
2025-06-10T12:22:26.593730Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.594153Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.594644Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_yoast_indexable`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.595317Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_yoast_indexable` because it could not be opened.
2025-06-10T12:22:26.595763Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.596047Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.596347Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.596727Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_yoast_indexable_hierarchy.ibd' OS error: 103
2025-06-10T12:22:26.597121Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.597393Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.597809Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_yoast_indexable_hierarchy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.598431Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_yoast_indexable_hierarchy` because it could not be opened.
2025-06-10T12:22:26.598845Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.599141Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.599409Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.599796Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_yoast_migrations.ibd' OS error: 103
2025-06-10T12:22:26.600164Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.600428Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.600872Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_yoast_migrations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.601460Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_yoast_migrations` because it could not be opened.
2025-06-10T12:22:26.601877Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.602176Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.602451Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.602843Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_yoast_primary_term.ibd' OS error: 103
2025-06-10T12:22:26.603233Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.603482Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.603904Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_yoast_primary_term`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.604514Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_yoast_primary_term` because it could not be opened.
2025-06-10T12:22:26.604885Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.605272Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.605601Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.606235Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_yoast_seo_links.ibd' OS error: 103
2025-06-10T12:22:26.606576Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.606833Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.607376Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_yoast_seo_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.607923Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_yoast_seo_links` because it could not be opened.
2025-06-10T12:22:26.608443Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.608695Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.608956Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.609425Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos1\wp_yoast_seo_meta.ibd' OS error: 103
2025-06-10T12:22:26.609742Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.609991Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.610569Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos1/wp_yoast_seo_meta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.611193Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos1/wp_yoast_seo_meta` because it could not be opened.
2025-06-10T12:22:26.611672Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.611939Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.612276Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.612653Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos2\wp_actionscheduler_actions.ibd' OS error: 103
2025-06-10T12:22:26.613079Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.613352Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.613801Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos2/wp_actionscheduler_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.614418Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos2/wp_actionscheduler_actions` because it could not be opened.
2025-06-10T12:22:26.614880Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.615163Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.615438Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.615827Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos2\wp_actionscheduler_claims.ibd' OS error: 103
2025-06-10T12:22:26.616255Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.616522Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.617204Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos2/wp_actionscheduler_claims`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.617853Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos2/wp_actionscheduler_claims` because it could not be opened.
2025-06-10T12:22:26.618354Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.618656Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.619044Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.619464Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos2\wp_actionscheduler_groups.ibd' OS error: 103
2025-06-10T12:22:26.619856Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.620221Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.620698Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos2/wp_actionscheduler_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.621323Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos2/wp_actionscheduler_groups` because it could not be opened.
2025-06-10T12:22:26.621773Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.622070Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.622347Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.622732Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos2\wp_actionscheduler_logs.ibd' OS error: 103
2025-06-10T12:22:26.623124Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.623399Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.623870Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos2/wp_actionscheduler_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.624530Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos2/wp_actionscheduler_logs` because it could not be opened.
2025-06-10T12:22:26.625059Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.625333Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.625607Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.626098Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos2\wp_canvas_notifications.ibd' OS error: 103
2025-06-10T12:22:26.626453Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.626719Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.627367Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos2/wp_canvas_notifications`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.628192Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos2/wp_canvas_notifications` because it could not be opened.
2025-06-10T12:22:26.628635Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.628980Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.629259Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.629619Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos2\wp_cscs_db_subscriptions.ibd' OS error: 103
2025-06-10T12:22:26.630060Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.630305Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.630696Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos2/wp_cscs_db_subscriptions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.631350Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos2/wp_cscs_db_subscriptions` because it could not be opened.
2025-06-10T12:22:26.631737Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.632109Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.632369Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.632733Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos2\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:26.633099Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.633355Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.633980Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos2/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.634516Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos2/wp_fbv` because it could not be opened.
2025-06-10T12:22:26.634976Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.635231Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.635486Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.635921Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos2\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:26.636324Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.636569Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.637020Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos2/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.637563Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos2/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:26.638025Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.638288Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.638557Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.639010Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos2\wp_itsec_bans.ibd' OS error: 103
2025-06-10T12:22:26.639336Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.639586Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.640046Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos2/wp_itsec_bans`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.640576Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos2/wp_itsec_bans` because it could not be opened.
2025-06-10T12:22:26.641017Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.641340Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.641610Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.642032Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos2\wp_itsec_distributed_storage.ibd' OS error: 103
2025-06-10T12:22:26.642391Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.642711Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.643187Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos2/wp_itsec_distributed_storage`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.643826Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos2/wp_itsec_distributed_storage` because it could not be opened.
2025-06-10T12:22:26.644286Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.644558Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.644884Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.645275Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos2\wp_itsec_fingerprints.ibd' OS error: 103
2025-06-10T12:22:26.645603Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.645902Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.646339Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos2/wp_itsec_fingerprints`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.646991Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos2/wp_itsec_fingerprints` because it could not be opened.
2025-06-10T12:22:26.647414Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.647748Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.648067Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.648992Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos2\wp_itsec_geolocation_cache.ibd' OS error: 103
2025-06-10T12:22:26.649333Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.649660Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.650661Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos2/wp_itsec_geolocation_cache`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.651298Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos2/wp_itsec_geolocation_cache` because it could not be opened.
2025-06-10T12:22:26.651769Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.652036Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.652311Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.652743Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos2\wp_itsec_lockouts.ibd' OS error: 103
2025-06-10T12:22:26.653079Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.653341Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.653815Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos2/wp_itsec_lockouts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.654405Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos2/wp_itsec_lockouts` because it could not be opened.
2025-06-10T12:22:26.655126Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.655419Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.655801Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.656174Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos2\wp_itsec_logs.ibd' OS error: 103
2025-06-10T12:22:26.656494Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.656869Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.657277Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos2/wp_itsec_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.657962Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos2/wp_itsec_logs` because it could not be opened.
2025-06-10T12:22:26.658389Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.658770Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.659031Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.659398Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos2\wp_itsec_mutexes.ibd' OS error: 103
2025-06-10T12:22:26.659797Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.660044Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.660440Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos2/wp_itsec_mutexes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.661095Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos2/wp_itsec_mutexes` because it could not be opened.
2025-06-10T12:22:26.661711Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.661987Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.662255Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.662725Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos2\wp_itsec_opaque_tokens.ibd' OS error: 103
2025-06-10T12:22:26.663058Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.663313Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.663816Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos2/wp_itsec_opaque_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.664371Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos2/wp_itsec_opaque_tokens` because it could not be opened.
2025-06-10T12:22:26.664837Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.665087Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.665345Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.665795Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos2\wp_itsec_temp.ibd' OS error: 103
2025-06-10T12:22:26.666099Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.666341Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.666809Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos2/wp_itsec_temp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.667566Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos2/wp_itsec_temp` because it could not be opened.
2025-06-10T12:22:26.667991Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.668251Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.668825Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.669200Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos2\wp_itsec_user_groups.ibd' OS error: 103
2025-06-10T12:22:26.669649Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.670044Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.670432Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos2/wp_itsec_user_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.671084Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos2/wp_itsec_user_groups` because it could not be opened.
2025-06-10T12:22:26.671455Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.671921Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.672176Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.672586Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos2\wp_mclean_refs.ibd' OS error: 103
2025-06-10T12:22:26.672919Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.673164Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.673649Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos2/wp_mclean_refs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.674279Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos2/wp_mclean_refs` because it could not be opened.
2025-06-10T12:22:26.674745Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.675062Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.675324Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.675746Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos2\wp_mclean_scan.ibd' OS error: 103
2025-06-10T12:22:26.676075Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.676336Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.676820Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos2/wp_mclean_scan`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.677355Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos2/wp_mclean_scan` because it could not be opened.
2025-06-10T12:22:26.677783Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.678036Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.678301Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.678737Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos2\wp_pms_member_subscriptionmeta.ibd' OS error: 103
2025-06-10T12:22:26.679086Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.679336Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.679839Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos2/wp_pms_member_subscriptionmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.680393Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos2/wp_pms_member_subscriptionmeta` because it could not be opened.
2025-06-10T12:22:26.680992Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.681263Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.681669Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.682088Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos2\wp_pms_member_subscriptions.ibd' OS error: 103
2025-06-10T12:22:26.682424Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.682806Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.683191Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos2/wp_pms_member_subscriptions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.683915Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos2/wp_pms_member_subscriptions` because it could not be opened.
2025-06-10T12:22:26.684338Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.684735Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.685130Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.685706Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos2\wp_pms_paymentmeta.ibd' OS error: 103
2025-06-10T12:22:26.686267Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.686634Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.687038Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos2/wp_pms_paymentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.687687Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos2/wp_pms_paymentmeta` because it could not be opened.
2025-06-10T12:22:26.688086Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.688343Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.688693Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.689060Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos2\wp_pms_payments.ibd' OS error: 103
2025-06-10T12:22:26.689377Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.689722Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.690145Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos2/wp_pms_payments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.690790Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos2/wp_pms_payments` because it could not be opened.
2025-06-10T12:22:26.691194Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.691518Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.691800Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.692242Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos2\wp_sb_integrations.ibd' OS error: 103
2025-06-10T12:22:26.692738Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.692992Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.693388Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos2/wp_sb_integrations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.694036Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos2/wp_sb_integrations` because it could not be opened.
2025-06-10T12:22:26.694428Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.694771Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.695034Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.695535Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos2\wp_socialbug_affiliates.ibd' OS error: 103
2025-06-10T12:22:26.696334Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.696589Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.697282Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos2/wp_socialbug_affiliates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.698124Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos2/wp_socialbug_affiliates` because it could not be opened.
2025-06-10T12:22:26.698617Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.698935Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.699281Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.699707Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos2\wp_wc_admin_note_actions.ibd' OS error: 103
2025-06-10T12:22:26.700108Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.700397Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.700827Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos2/wp_wc_admin_note_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.701517Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos2/wp_wc_admin_note_actions` because it could not be opened.
2025-06-10T12:22:26.702008Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.702310Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.702599Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.702998Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos2\wp_wc_admin_notes.ibd' OS error: 103
2025-06-10T12:22:26.703383Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.703721Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.704224Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos2/wp_wc_admin_notes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.704875Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos2/wp_wc_admin_notes` because it could not be opened.
2025-06-10T12:22:26.705450Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.705898Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.706447Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.706867Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos2\wp_wc_category_lookup.ibd' OS error: 103
2025-06-10T12:22:26.707294Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.707565Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.707975Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos2/wp_wc_category_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.708784Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos2/wp_wc_category_lookup` because it could not be opened.
2025-06-10T12:22:26.709289Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.709552Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.709822Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.710309Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos2\wp_wc_customer_lookup.ibd' OS error: 103
2025-06-10T12:22:26.710651Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.710910Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.711336Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos2/wp_wc_customer_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.711908Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos2/wp_wc_customer_lookup` because it could not be opened.
2025-06-10T12:22:26.712493Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.712753Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.713043Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.713467Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos2\wp_wc_order_coupon_lookup.ibd' OS error: 103
2025-06-10T12:22:26.713799Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.714111Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.714529Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos2/wp_wc_order_coupon_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.715165Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos2/wp_wc_order_coupon_lookup` because it could not be opened.
2025-06-10T12:22:26.715631Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.715880Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.716218Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.716611Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos2\wp_wc_order_product_lookup.ibd' OS error: 103
2025-06-10T12:22:26.716941Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.717367Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.717794Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos2/wp_wc_order_product_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.718635Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos2/wp_wc_order_product_lookup` because it could not be opened.
2025-06-10T12:22:26.719136Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.719415Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.719676Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.720157Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos2\wp_wc_order_stats.ibd' OS error: 103
2025-06-10T12:22:26.720479Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.720728Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.721213Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos2/wp_wc_order_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.721763Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos2/wp_wc_order_stats` because it could not be opened.
2025-06-10T12:22:26.722290Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.722680Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.723172Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.723721Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos2\wp_wc_order_tax_lookup.ibd' OS error: 103
2025-06-10T12:22:26.724370Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.724652Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.725100Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos2/wp_wc_order_tax_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.725679Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos2/wp_wc_order_tax_lookup` because it could not be opened.
2025-06-10T12:22:26.726170Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.726464Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.726753Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.727185Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos2\wp_wc_reserved_stock.ibd' OS error: 103
2025-06-10T12:22:26.727530Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.727797Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.728275Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos2/wp_wc_reserved_stock`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.729447Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos2/wp_wc_reserved_stock` because it could not be opened.
2025-06-10T12:22:26.729922Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.730281Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.730558Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.731180Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos2\wp_woo_ua_auction_log.ibd' OS error: 103
2025-06-10T12:22:26.731543Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.731806Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.732258Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos2/wp_woo_ua_auction_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.732840Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos2/wp_woo_ua_auction_log` because it could not be opened.
2025-06-10T12:22:26.733337Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.733744Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.734083Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.734475Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos2\wp_wpam_actions.ibd' OS error: 103
2025-06-10T12:22:26.734808Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.735179Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.735600Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos2/wp_wpam_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.736261Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos2/wp_wpam_actions` because it could not be opened.
2025-06-10T12:22:26.736700Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.737240Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.737537Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.737957Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos2\wp_wpam_affiliates.ibd' OS error: 103
2025-06-10T12:22:26.738437Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.738690Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.739172Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos2/wp_wpam_affiliates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.739767Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos2/wp_wpam_affiliates` because it could not be opened.
2025-06-10T12:22:26.740213Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.740480Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.740748Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.741173Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos2\wp_wpam_affiliates_fields.ibd' OS error: 103
2025-06-10T12:22:26.741528Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.741790Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.742263Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos2/wp_wpam_affiliates_fields`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.742846Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos2/wp_wpam_affiliates_fields` because it could not be opened.
2025-06-10T12:22:26.743303Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.743561Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.743820Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.744275Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos2\wp_wpam_creatives.ibd' OS error: 103
2025-06-10T12:22:26.744591Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.744843Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.745323Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos2/wp_wpam_creatives`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.746067Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos2/wp_wpam_creatives` because it could not be opened.
2025-06-10T12:22:26.746474Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.746728Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.747098Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.747497Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos2\wp_wpam_events.ibd' OS error: 103
2025-06-10T12:22:26.747813Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.748131Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.748603Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos2/wp_wpam_events`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.749256Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos2/wp_wpam_events` because it could not be opened.
2025-06-10T12:22:26.749952Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.750393Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.750695Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.751160Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos2\wp_wpam_impressions.ibd' OS error: 103
2025-06-10T12:22:26.751610Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.751977Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.752421Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos2/wp_wpam_impressions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.753092Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos2/wp_wpam_impressions` because it could not be opened.
2025-06-10T12:22:26.753482Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.753833Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.754155Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.754533Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos2\wp_wpam_messages.ibd' OS error: 103
2025-06-10T12:22:26.754879Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.755294Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.755816Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos2/wp_wpam_messages`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.756518Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos2/wp_wpam_messages` because it could not be opened.
2025-06-10T12:22:26.757121Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.757419Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.757728Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.758166Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos2\wp_wpam_paypal_logs.ibd' OS error: 103
2025-06-10T12:22:26.758493Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.758745Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.759220Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos2/wp_wpam_paypal_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.759796Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos2/wp_wpam_paypal_logs` because it could not be opened.
2025-06-10T12:22:26.760691Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.761114Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.762316Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.762973Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos2\wp_wpam_tracking_tokens.ibd' OS error: 103
2025-06-10T12:22:26.763550Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.763987Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.764722Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos2/wp_wpam_tracking_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.765372Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos2/wp_wpam_tracking_tokens` because it could not be opened.
2025-06-10T12:22:26.765887Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.766165Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.766443Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.766874Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos2\wp_wpam_tracking_tokens_purchase_logs.ibd' OS error: 103
2025-06-10T12:22:26.767263Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.767534Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.768019Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos2/wp_wpam_tracking_tokens_purchase_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.768649Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos2/wp_wpam_tracking_tokens_purchase_logs` because it could not be opened.
2025-06-10T12:22:26.769252Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.769537Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.769875Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.770306Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos2\wp_wpam_transactions.ibd' OS error: 103
2025-06-10T12:22:26.770655Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.770959Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.771463Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos2/wp_wpam_transactions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.772075Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos2/wp_wpam_transactions` because it could not be opened.
2025-06-10T12:22:26.772511Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.772840Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.773114Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.773501Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos2\wp_yoast_indexable.ibd' OS error: 103
2025-06-10T12:22:26.773905Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.774170Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.774586Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos2/wp_yoast_indexable`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.775215Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos2/wp_yoast_indexable` because it could not be opened.
2025-06-10T12:22:26.775611Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.775958Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.776234Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.776625Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos2\wp_yoast_indexable_hierarchy.ibd' OS error: 103
2025-06-10T12:22:26.777058Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.777345Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.777856Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos2/wp_yoast_indexable_hierarchy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.778444Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos2/wp_yoast_indexable_hierarchy` because it could not be opened.
2025-06-10T12:22:26.778920Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.779176Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.779438Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.779862Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos2\wp_yoast_migrations.ibd' OS error: 103
2025-06-10T12:22:26.780200Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.780452Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.780909Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos2/wp_yoast_migrations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.781460Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos2/wp_yoast_migrations` because it could not be opened.
2025-06-10T12:22:26.781907Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.782192Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.782455Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.782912Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos2\wp_yoast_primary_term.ibd' OS error: 103
2025-06-10T12:22:26.783239Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.783518Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.783977Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos2/wp_yoast_primary_term`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.784533Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos2/wp_yoast_primary_term` because it could not be opened.
2025-06-10T12:22:26.784965Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.785220Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.785481Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.785998Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos2\wp_yoast_seo_links.ibd' OS error: 103
2025-06-10T12:22:26.786340Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.786605Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.787050Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos2/wp_yoast_seo_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.787661Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos2/wp_yoast_seo_links` because it could not be opened.
2025-06-10T12:22:26.788120Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.788380Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.788732Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.789154Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos2\wp_yoast_seo_meta.ibd' OS error: 103
2025-06-10T12:22:26.789524Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.789913Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.790308Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos2/wp_yoast_seo_meta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.790947Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos2/wp_yoast_seo_meta` because it could not be opened.
2025-06-10T12:22:26.791723Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.792875Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.793382Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.793885Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos3\wp_cscs_db_subscriptions.ibd' OS error: 103
2025-06-10T12:22:26.794356Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.794840Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.795294Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos3/wp_cscs_db_subscriptions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.795928Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos3/wp_cscs_db_subscriptions` because it could not be opened.
2025-06-10T12:22:26.796452Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.796741Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.797019Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.797409Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos3\wp_itsec_distributed_storage.ibd' OS error: 103
2025-06-10T12:22:26.797798Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.798127Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.798558Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos3/wp_itsec_distributed_storage`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.799229Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos3/wp_itsec_distributed_storage` because it could not be opened.
2025-06-10T12:22:26.800053Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.800367Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.800648Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.801098Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos3\wp_itsec_fingerprints.ibd' OS error: 103
2025-06-10T12:22:26.801450Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.801788Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.802255Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos3/wp_itsec_fingerprints`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.802929Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos3/wp_itsec_fingerprints` because it could not be opened.
2025-06-10T12:22:26.803393Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.803655Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.803989Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.804357Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos3\wp_itsec_geolocation_cache.ibd' OS error: 103
2025-06-10T12:22:26.804734Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.805057Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.805513Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos3/wp_itsec_geolocation_cache`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.806172Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos3/wp_itsec_geolocation_cache` because it could not be opened.
2025-06-10T12:22:26.806614Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.806933Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.807232Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.807632Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos3\wp_itsec_lockouts.ibd' OS error: 103
2025-06-10T12:22:26.808047Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.808303Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.808801Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos3/wp_itsec_lockouts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.809448Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos3/wp_itsec_lockouts` because it could not be opened.
2025-06-10T12:22:26.809933Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.810211Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.810483Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.810895Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos3\wp_itsec_logs.ibd' OS error: 103
2025-06-10T12:22:26.811226Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.811491Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.811938Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos3/wp_itsec_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.812511Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos3/wp_itsec_logs` because it could not be opened.
2025-06-10T12:22:26.812947Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.813252Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.813534Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.813939Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos3\wp_itsec_mutexes.ibd' OS error: 103
2025-06-10T12:22:26.814326Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.814622Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.815088Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos3/wp_itsec_mutexes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.815707Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos3/wp_itsec_mutexes` because it could not be opened.
2025-06-10T12:22:26.816130Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.816405Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.816714Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.817108Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos3\wp_itsec_opaque_tokens.ibd' OS error: 103
2025-06-10T12:22:26.817464Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.817766Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.818188Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos3/wp_itsec_opaque_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.818887Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos3/wp_itsec_opaque_tokens` because it could not be opened.
2025-06-10T12:22:26.819377Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.819672Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.819952Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.820341Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos3\wp_itsec_temp.ibd' OS error: 103
2025-06-10T12:22:26.820739Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.821009Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.821426Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos3/wp_itsec_temp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.822034Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos3/wp_itsec_temp` because it could not be opened.
2025-06-10T12:22:26.822443Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.822736Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.823008Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.823429Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos3\wp_itsec_user_groups.ibd' OS error: 103
2025-06-10T12:22:26.823781Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.824496Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.824910Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos3/wp_itsec_user_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.825609Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos3/wp_itsec_user_groups` because it could not be opened.
2025-06-10T12:22:26.826466Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.826776Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.827086Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.827588Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos3\wp_yoast_seo_links.ibd' OS error: 103
2025-06-10T12:22:26.827965Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.828266Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.828787Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos3/wp_yoast_seo_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.829485Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos3/wp_yoast_seo_links` because it could not be opened.
2025-06-10T12:22:26.829968Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.830250Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.830587Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.830979Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos3\wp_yoast_seo_meta.ibd' OS error: 103
2025-06-10T12:22:26.831334Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.831702Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.832148Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos3/wp_yoast_seo_meta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.832836Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos3/wp_yoast_seo_meta` because it could not be opened.
2025-06-10T12:22:26.833322Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.833768Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.834068Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.834579Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos4\wp_actionscheduler_actions.ibd' OS error: 103
2025-06-10T12:22:26.834966Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.835237Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.835733Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos4/wp_actionscheduler_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.836313Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos4/wp_actionscheduler_actions` because it could not be opened.
2025-06-10T12:22:26.836840Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.837099Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.837393Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.837831Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos4\wp_actionscheduler_claims.ibd' OS error: 103
2025-06-10T12:22:26.838172Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.838472Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.838880Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos4/wp_actionscheduler_claims`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.839504Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos4/wp_actionscheduler_claims` because it could not be opened.
2025-06-10T12:22:26.839888Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.840286Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.840646Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.841016Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos4\wp_actionscheduler_groups.ibd' OS error: 103
2025-06-10T12:22:26.841414Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.841766Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.842156Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos4/wp_actionscheduler_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.842942Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos4/wp_actionscheduler_groups` because it could not be opened.
2025-06-10T12:22:26.843437Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.843810Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.844141Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.844582Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos4\wp_actionscheduler_logs.ibd' OS error: 103
2025-06-10T12:22:26.844934Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.845197Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.845685Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos4/wp_actionscheduler_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.846450Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos4/wp_actionscheduler_logs` because it could not be opened.
2025-06-10T12:22:26.846913Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.847179Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.847529Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.847965Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos4\wp_cscs_db_subscriptions.ibd' OS error: 103
2025-06-10T12:22:26.848377Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.848685Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.849112Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos4/wp_cscs_db_subscriptions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.849744Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos4/wp_cscs_db_subscriptions` because it could not be opened.
2025-06-10T12:22:26.850168Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.854516Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.854875Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.855339Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos4\wp_itsec_distributed_storage.ibd' OS error: 103
2025-06-10T12:22:26.855752Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.856080Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.856672Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos4/wp_itsec_distributed_storage`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.857409Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos4/wp_itsec_distributed_storage` because it could not be opened.
2025-06-10T12:22:26.858101Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.858403Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.858799Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.859185Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos4\wp_itsec_fingerprints.ibd' OS error: 103
2025-06-10T12:22:26.859558Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.859840Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.860263Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos4/wp_itsec_fingerprints`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.860897Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos4/wp_itsec_fingerprints` because it could not be opened.
2025-06-10T12:22:26.861328Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.861596Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.861900Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.862287Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos4\wp_itsec_geolocation_cache.ibd' OS error: 103
2025-06-10T12:22:26.862647Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.862960Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.863386Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos4/wp_itsec_geolocation_cache`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.864039Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos4/wp_itsec_geolocation_cache` because it could not be opened.
2025-06-10T12:22:26.864499Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.864818Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.865122Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.865523Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos4\wp_itsec_lockouts.ibd' OS error: 103
2025-06-10T12:22:26.865983Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.866282Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.866762Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos4/wp_itsec_lockouts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.867591Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos4/wp_itsec_lockouts` because it could not be opened.
2025-06-10T12:22:26.868105Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.868383Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.868682Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.869085Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos4\wp_itsec_logs.ibd' OS error: 103
2025-06-10T12:22:26.869414Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.869676Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.870125Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos4/wp_itsec_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.870690Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos4/wp_itsec_logs` because it could not be opened.
2025-06-10T12:22:26.871109Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.871372Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.871643Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.872049Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos4\wp_itsec_mutexes.ibd' OS error: 103
2025-06-10T12:22:26.872435Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.872797Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.873247Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos4/wp_itsec_mutexes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.873883Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos4/wp_itsec_mutexes` because it could not be opened.
2025-06-10T12:22:26.874274Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.874534Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.874942Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.875315Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos4\wp_itsec_opaque_tokens.ibd' OS error: 103
2025-06-10T12:22:26.875653Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.876021Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.876414Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos4/wp_itsec_opaque_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.877062Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos4/wp_itsec_opaque_tokens` because it could not be opened.
2025-06-10T12:22:26.877445Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.877765Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.878085Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.878446Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos4\wp_itsec_temp.ibd' OS error: 103
2025-06-10T12:22:26.878844Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.879095Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.879487Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos4/wp_itsec_temp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.880135Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos4/wp_itsec_temp` because it could not be opened.
2025-06-10T12:22:26.880590Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.880927Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.881199Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.881570Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos4\wp_itsec_user_groups.ibd' OS error: 103
2025-06-10T12:22:26.881977Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.882232Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.882632Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos4/wp_itsec_user_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.883343Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos4/wp_itsec_user_groups` because it could not be opened.
2025-06-10T12:22:26.883789Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.884070Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.884355Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.884803Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos4\wp_mycred_log.ibd' OS error: 103
2025-06-10T12:22:26.885140Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.885406Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.885934Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos4/wp_mycred_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.886494Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos4/wp_mycred_log` because it could not be opened.
2025-06-10T12:22:26.886943Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.887211Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.887549Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.888045Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos4\wp_pms_member_subscriptionmeta.ibd' OS error: 103
2025-06-10T12:22:26.888589Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.889057Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.889466Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos4/wp_pms_member_subscriptionmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.890179Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos4/wp_pms_member_subscriptionmeta` because it could not be opened.
2025-06-10T12:22:26.890803Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.891085Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.891365Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.891825Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos4\wp_pms_member_subscriptions.ibd' OS error: 103
2025-06-10T12:22:26.892186Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.892495Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.893002Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos4/wp_pms_member_subscriptions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.893665Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos4/wp_pms_member_subscriptions` because it could not be opened.
2025-06-10T12:22:26.894205Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.894551Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.894835Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.895210Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos4\wp_pms_paymentmeta.ibd' OS error: 103
2025-06-10T12:22:26.895622Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.895895Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.896358Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos4/wp_pms_paymentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.897299Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos4/wp_pms_paymentmeta` because it could not be opened.
2025-06-10T12:22:26.898050Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.898326Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.898673Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.899037Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos4\wp_pms_payments.ibd' OS error: 103
2025-06-10T12:22:26.899362Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.899672Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.900096Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos4/wp_pms_payments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.900727Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos4/wp_pms_payments` because it could not be opened.
2025-06-10T12:22:26.901102Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.901439Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.901912Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.902302Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos4\wp_sb_integrations.ibd' OS error: 103
2025-06-10T12:22:26.902790Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.903071Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.903553Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos4/wp_sb_integrations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.904092Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos4/wp_sb_integrations` because it could not be opened.
2025-06-10T12:22:26.904636Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.904899Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.905149Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.905603Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos4\wp_socialbug_affiliates.ibd' OS error: 103
2025-06-10T12:22:26.905926Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.906200Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.906751Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos4/wp_socialbug_affiliates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.907403Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos4/wp_socialbug_affiliates` because it could not be opened.
2025-06-10T12:22:26.907858Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.908364Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.908726Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.909095Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos4\wp_wc_admin_note_actions.ibd' OS error: 103
2025-06-10T12:22:26.909620Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.909884Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.910322Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos4/wp_wc_admin_note_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.910971Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos4/wp_wc_admin_note_actions` because it could not be opened.
2025-06-10T12:22:26.911406Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.911747Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.912008Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.912420Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos4\wp_wc_admin_notes.ibd' OS error: 103
2025-06-10T12:22:26.912765Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.913011Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.913503Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos4/wp_wc_admin_notes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.914146Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos4/wp_wc_admin_notes` because it could not be opened.
2025-06-10T12:22:26.914816Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.915158Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.915541Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.915973Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos4\wp_wc_category_lookup.ibd' OS error: 103
2025-06-10T12:22:26.916321Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.916663Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.917128Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos4/wp_wc_category_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.917757Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos4/wp_wc_category_lookup` because it could not be opened.
2025-06-10T12:22:26.918162Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.918492Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.918751Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.919110Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos4\wp_wc_customer_lookup.ibd' OS error: 103
2025-06-10T12:22:26.919733Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.920366Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.921049Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos4/wp_wc_customer_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.922571Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos4/wp_wc_customer_lookup` because it could not be opened.
2025-06-10T12:22:26.923328Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.923654Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.923929Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.924337Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos4\wp_wc_order_coupon_lookup.ibd' OS error: 103
2025-06-10T12:22:26.924729Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.925149Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.925660Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos4/wp_wc_order_coupon_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.926259Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos4/wp_wc_order_coupon_lookup` because it could not be opened.
2025-06-10T12:22:26.926909Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.927170Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.927435Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.927940Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos4\wp_wc_order_product_lookup.ibd' OS error: 103
2025-06-10T12:22:26.928289Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.928652Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.929093Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos4/wp_wc_order_product_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.929922Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos4/wp_wc_order_product_lookup` because it could not be opened.
2025-06-10T12:22:26.930494Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.930856Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.931124Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.931501Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos4\wp_wc_order_stats.ibd' OS error: 103
2025-06-10T12:22:26.931982Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.932272Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.933093Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos4/wp_wc_order_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.933834Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos4/wp_wc_order_stats` because it could not be opened.
2025-06-10T12:22:26.934315Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.934642Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.934935Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.935325Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos4\wp_wc_order_tax_lookup.ibd' OS error: 103
2025-06-10T12:22:26.935729Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.935992Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.936405Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos4/wp_wc_order_tax_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.937027Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos4/wp_wc_order_tax_lookup` because it could not be opened.
2025-06-10T12:22:26.937461Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.937758Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.938033Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.938417Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos4\wp_wc_reserved_stock.ibd' OS error: 103
2025-06-10T12:22:26.938791Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.939053Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.939467Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos4/wp_wc_reserved_stock`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.940073Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos4/wp_wc_reserved_stock` because it could not be opened.
2025-06-10T12:22:26.940460Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.940751Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.941022Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.941403Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos4\wp_yoast_seo_links.ibd' OS error: 103
2025-06-10T12:22:26.941767Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.942122Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.942610Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos4/wp_yoast_seo_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.943182Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos4/wp_yoast_seo_links` because it could not be opened.
2025-06-10T12:22:26.943823Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.944099Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.944372Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.944785Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sfos4\wp_yoast_seo_meta.ibd' OS error: 103
2025-06-10T12:22:26.945124Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.945390Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.945844Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sfos4/wp_yoast_seo_meta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.946416Z 0 [Warning] InnoDB: Ignoring tablespace `client_sfos4/wp_yoast_seo_meta` because it could not be opened.
2025-06-10T12:22:26.947064Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.947341Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.947642Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.948217Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_actionscheduler_actions.ibd' OS error: 103
2025-06-10T12:22:26.948689Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.948947Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.949348Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_actionscheduler_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.950052Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_actionscheduler_actions` because it could not be opened.
2025-06-10T12:22:26.950561Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.950853Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.951115Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.951598Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_actionscheduler_claims.ibd' OS error: 103
2025-06-10T12:22:26.951989Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.952241Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.952733Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_actionscheduler_claims`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.953311Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_actionscheduler_claims` because it could not be opened.
2025-06-10T12:22:26.953847Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.954440Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.954771Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.955144Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_actionscheduler_groups.ibd' OS error: 103
2025-06-10T12:22:26.955604Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.955909Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.956306Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_actionscheduler_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.956965Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_actionscheduler_groups` because it could not be opened.
2025-06-10T12:22:26.957369Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.957750Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.958007Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.958453Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_actionscheduler_logs.ibd' OS error: 103
2025-06-10T12:22:26.958855Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.959118Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.959608Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_actionscheduler_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.960404Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_actionscheduler_logs` because it could not be opened.
2025-06-10T12:22:26.960940Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.961202Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.961526Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.961918Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:26.962247Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.962584Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.963023Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.963656Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:26.964084Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.964372Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.964733Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.965228Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_comments.ibd' OS error: 103
2025-06-10T12:22:26.965655Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.965907Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.966522Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.967341Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_comments` because it could not be opened.
2025-06-10T12:22:26.967839Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.968265Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.968539Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.969170Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:26.969527Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.970257Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.970673Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.971286Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_fbv` because it could not be opened.
2025-06-10T12:22:26.971707Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.971971Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.972323Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.972706Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:26.973075Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.973565Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.974017Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.974721Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:26.975309Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.975589Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.975873Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.976349Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_links.ibd' OS error: 103
2025-06-10T12:22:26.976696Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.976969Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.977518Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.978076Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_links` because it could not be opened.
2025-06-10T12:22:26.978593Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.978847Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.979218Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.979656Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_options.ibd' OS error: 103
2025-06-10T12:22:26.979970Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.980313Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.980720Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.981450Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_options` because it could not be opened.
2025-06-10T12:22:26.981882Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.982249Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.982526Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.982892Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:26.983343Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.983613Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.984062Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.984726Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_postmeta` because it could not be opened.
2025-06-10T12:22:26.985185Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.985454Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.985724Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.986127Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_posts.ibd' OS error: 103
2025-06-10T12:22:26.986516Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.986787Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.987216Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.987780Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_posts` because it could not be opened.
2025-06-10T12:22:26.988223Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.988485Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.988811Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.989285Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_revslider_css.ibd' OS error: 103
2025-06-10T12:22:26.989633Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.989893Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.990394Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_revslider_css`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.990964Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_revslider_css` because it could not be opened.
2025-06-10T12:22:26.991484Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.991803Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.992103Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.992541Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_revslider_css_bkp.ibd' OS error: 103
2025-06-10T12:22:26.992884Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.993208Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.993613Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_revslider_css_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.994250Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_revslider_css_bkp` because it could not be opened.
2025-06-10T12:22:26.994663Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.994928Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.995288Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.995663Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_revslider_layer_animations.ibd' OS error: 103
2025-06-10T12:22:26.996039Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.996531Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:26.996954Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_revslider_layer_animations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:26.997663Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_revslider_layer_animations` because it could not be opened.
2025-06-10T12:22:26.998151Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:26.998447Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:26.998745Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:26.999192Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_revslider_layer_animations_bkp.ibd' OS error: 103
2025-06-10T12:22:26.999600Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:26.999871Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.000349Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_revslider_layer_animations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.001067Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_revslider_layer_animations_bkp` because it could not be opened.
2025-06-10T12:22:27.002165Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.002496Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.002988Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.003396Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_revslider_navigations.ibd' OS error: 103
2025-06-10T12:22:27.003810Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.004106Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.004530Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_revslider_navigations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.005181Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_revslider_navigations` because it could not be opened.
2025-06-10T12:22:27.005635Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.005940Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.006241Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.006640Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_revslider_navigations_bkp.ibd' OS error: 103
2025-06-10T12:22:27.007041Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.007319Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.007786Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_revslider_navigations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.008435Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_revslider_navigations_bkp` because it could not be opened.
2025-06-10T12:22:27.009041Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.009355Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.009833Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.010298Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_revslider_sliders.ibd' OS error: 103
2025-06-10T12:22:27.010675Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.011031Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.011530Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_revslider_sliders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.012193Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_revslider_sliders` because it could not be opened.
2025-06-10T12:22:27.012635Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.012972Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.013455Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.013913Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_revslider_sliders_bkp.ibd' OS error: 103
2025-06-10T12:22:27.014256Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.014505Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.014958Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_revslider_sliders_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.015526Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_revslider_sliders_bkp` because it could not be opened.
2025-06-10T12:22:27.015990Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.016244Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.016502Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.017010Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_revslider_slides.ibd' OS error: 103
2025-06-10T12:22:27.017458Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.017757Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.018206Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_revslider_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.018855Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_revslider_slides` because it could not be opened.
2025-06-10T12:22:27.019280Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.019538Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.019967Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.020379Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_revslider_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:27.020777Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.021046Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.021446Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_revslider_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.022250Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_revslider_slides_bkp` because it could not be opened.
2025-06-10T12:22:27.022786Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.023061Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.023328Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.023776Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_revslider_static_slides.ibd' OS error: 103
2025-06-10T12:22:27.024145Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.024398Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.024892Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_revslider_static_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.025470Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_revslider_static_slides` because it could not be opened.
2025-06-10T12:22:27.026063Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.026343Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.026607Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.027026Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_revslider_static_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:27.027387Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.027639Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.028162Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_revslider_static_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.029099Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_revslider_static_slides_bkp` because it could not be opened.
2025-06-10T12:22:27.029632Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.029993Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.030268Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.030703Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:27.031087Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.031353Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.031968Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.032747Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:27.033389Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.033852Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.034139Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.034666Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:27.035029Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.035372Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.035842Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.036441Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:27.036909Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.037181Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.037459Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.037906Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:27.038329Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.038589Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.039424Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.040626Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_termmeta` because it could not be opened.
2025-06-10T12:22:27.041307Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.041816Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.042233Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.043099Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_terms.ibd' OS error: 103
2025-06-10T12:22:27.043535Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.043975Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.044475Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.045090Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_terms` because it could not be opened.
2025-06-10T12:22:27.045519Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.045852Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.046282Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.046780Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:27.047264Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.047535Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.047988Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.048529Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_usermeta` because it could not be opened.
2025-06-10T12:22:27.049059Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.049317Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.049578Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.050066Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_users.ibd' OS error: 103
2025-06-10T12:22:27.050399Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.050764Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.051177Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.051810Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_users` because it could not be opened.
2025-06-10T12:22:27.052245Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.052514Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.052868Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.053234Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_wc_admin_note_actions.ibd' OS error: 103
2025-06-10T12:22:27.053578Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.053935Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.054323Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_wc_admin_note_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.054973Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_wc_admin_note_actions` because it could not be opened.
2025-06-10T12:22:27.055415Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.055763Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.056067Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.056620Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_wc_admin_notes.ibd' OS error: 103
2025-06-10T12:22:27.057049Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.057383Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.057883Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_wc_admin_notes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.058458Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_wc_admin_notes` because it could not be opened.
2025-06-10T12:22:27.059040Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.059316Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.059610Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.060038Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_wc_category_lookup.ibd' OS error: 103
2025-06-10T12:22:27.060476Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.060819Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.061222Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_wc_category_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.061907Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_wc_category_lookup` because it could not be opened.
2025-06-10T12:22:27.062370Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.062795Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.063135Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.063701Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_wc_customer_lookup.ibd' OS error: 103
2025-06-10T12:22:27.064218Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.064510Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.064955Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_wc_customer_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.065689Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_wc_customer_lookup` because it could not be opened.
2025-06-10T12:22:27.066227Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.066634Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.067306Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.067765Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_wc_download_log.ibd' OS error: 103
2025-06-10T12:22:27.068285Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.068550Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.069056Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_wc_download_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.069659Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_wc_download_log` because it could not be opened.
2025-06-10T12:22:27.070209Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.070474Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.070749Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.071241Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_wc_order_coupon_lookup.ibd' OS error: 103
2025-06-10T12:22:27.071691Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.072063Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.072490Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_wc_order_coupon_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.073408Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_wc_order_coupon_lookup` because it could not be opened.
2025-06-10T12:22:27.074126Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.074432Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.074728Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.075467Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_wc_order_product_lookup.ibd' OS error: 103
2025-06-10T12:22:27.076320Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.076835Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.077948Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_wc_order_product_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.078687Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_wc_order_product_lookup` because it could not be opened.
2025-06-10T12:22:27.079495Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.080031Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.080322Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.080694Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_wc_order_stats.ibd' OS error: 103
2025-06-10T12:22:27.081134Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.081567Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.082115Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_wc_order_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.082687Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_wc_order_stats` because it could not be opened.
2025-06-10T12:22:27.083207Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.083466Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.083791Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.084240Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_wc_order_tax_lookup.ibd' OS error: 103
2025-06-10T12:22:27.084582Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.084831Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.085359Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_wc_order_tax_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.086081Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_wc_order_tax_lookup` because it could not be opened.
2025-06-10T12:22:27.086513Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.086820Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.087204Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.087689Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_wc_product_meta_lookup.ibd' OS error: 103
2025-06-10T12:22:27.088158Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.088417Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.088905Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_wc_product_meta_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.089547Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_wc_product_meta_lookup` because it could not be opened.
2025-06-10T12:22:27.090087Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.090364Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.090677Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.091183Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_wc_reserved_stock.ibd' OS error: 103
2025-06-10T12:22:27.091529Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.091781Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.092440Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_wc_reserved_stock`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.093376Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_wc_reserved_stock` because it could not be opened.
2025-06-10T12:22:27.093959Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.094277Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.094542Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.095101Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_wc_tax_rate_classes.ibd' OS error: 103
2025-06-10T12:22:27.095476Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.095728Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.096259Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_wc_tax_rate_classes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.098516Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_wc_tax_rate_classes` because it could not be opened.
2025-06-10T12:22:27.099258Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.099643Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.099944Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.100413Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_wc_webhooks.ibd' OS error: 103
2025-06-10T12:22:27.100895Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.101211Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.101633Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_wc_webhooks`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.102253Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_wc_webhooks` because it could not be opened.
2025-06-10T12:22:27.102681Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.102949Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.103294Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.103821Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_woocommerce_api_keys.ibd' OS error: 103
2025-06-10T12:22:27.104376Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.104661Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.105139Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_woocommerce_api_keys`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.105848Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_woocommerce_api_keys` because it could not be opened.
2025-06-10T12:22:27.106592Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.106972Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.107451Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.107971Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_woocommerce_attribute_taxonomies.ibd' OS error: 103
2025-06-10T12:22:27.108575Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.108867Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.109409Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_woocommerce_attribute_taxonomies`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.110168Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_woocommerce_attribute_taxonomies` because it could not be opened.
2025-06-10T12:22:27.110794Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.111138Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.111658Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.112043Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_woocommerce_downloadable_product_permissions.ibd' OS error: 103
2025-06-10T12:22:27.112596Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.112851Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.113381Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_woocommerce_downloadable_product_permissions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.114004Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_woocommerce_downloadable_product_permissions` because it could not be opened.
2025-06-10T12:22:27.114667Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.114942Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.115444Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.115840Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_woocommerce_log.ibd' OS error: 103
2025-06-10T12:22:27.116323Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.116642Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.117126Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_woocommerce_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.117724Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_woocommerce_log` because it could not be opened.
2025-06-10T12:22:27.118225Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.118588Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.118894Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.119317Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_woocommerce_order_itemmeta.ibd' OS error: 103
2025-06-10T12:22:27.119689Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.119954Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.120403Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_woocommerce_order_itemmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.121126Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_woocommerce_order_itemmeta` because it could not be opened.
2025-06-10T12:22:27.121784Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.122239Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.122643Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.123277Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_woocommerce_order_items.ibd' OS error: 103
2025-06-10T12:22:27.123835Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.124280Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.124717Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_woocommerce_order_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.125418Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_woocommerce_order_items` because it could not be opened.
2025-06-10T12:22:27.125893Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.126254Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.126532Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.126915Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_woocommerce_payment_tokenmeta.ibd' OS error: 103
2025-06-10T12:22:27.127360Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.127624Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.128148Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_woocommerce_payment_tokenmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.129546Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_woocommerce_payment_tokenmeta` because it could not be opened.
2025-06-10T12:22:27.130509Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.131138Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.131519Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.131972Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_woocommerce_payment_tokens.ibd' OS error: 103
2025-06-10T12:22:27.132402Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.132781Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.133223Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_woocommerce_payment_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.133894Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_woocommerce_payment_tokens` because it could not be opened.
2025-06-10T12:22:27.134688Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.134969Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.135245Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.135706Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_woocommerce_sessions.ibd' OS error: 103
2025-06-10T12:22:27.136061Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.136378Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.136872Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_woocommerce_sessions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.137828Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_woocommerce_sessions` because it could not be opened.
2025-06-10T12:22:27.138483Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.138890Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.139216Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.139859Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_woocommerce_shipping_zone_locations.ibd' OS error: 103
2025-06-10T12:22:27.140575Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.140996Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.141693Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_woocommerce_shipping_zone_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.142706Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_woocommerce_shipping_zone_locations` because it could not be opened.
2025-06-10T12:22:27.143620Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.143889Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.144149Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.144627Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_woocommerce_shipping_zone_methods.ibd' OS error: 103
2025-06-10T12:22:27.145101Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.145409Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.145829Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_woocommerce_shipping_zone_methods`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.146557Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_woocommerce_shipping_zone_methods` because it could not be opened.
2025-06-10T12:22:27.147031Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.147348Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.147627Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.147984Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_woocommerce_shipping_zones.ibd' OS error: 103
2025-06-10T12:22:27.148450Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.148744Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.149124Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_woocommerce_shipping_zones`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.149996Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_woocommerce_shipping_zones` because it could not be opened.
2025-06-10T12:22:27.150550Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.150838Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.151121Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.151590Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_woocommerce_tax_rate_locations.ibd' OS error: 103
2025-06-10T12:22:27.151966Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.152264Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.152717Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_woocommerce_tax_rate_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.153563Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_woocommerce_tax_rate_locations` because it could not be opened.
2025-06-10T12:22:27.154394Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.154766Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.155044Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.155554Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_woocommerce_tax_rates.ibd' OS error: 103
2025-06-10T12:22:27.155898Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.156146Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.156822Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_woocommerce_tax_rates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.157607Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_woocommerce_tax_rates` because it could not be opened.
2025-06-10T12:22:27.158090Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.158576Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.158831Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.159188Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:27.159658Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.159910Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.160461Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.161343Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:27.162866Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.163136Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.163455Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.163873Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:27.164263Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.164714Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.165241Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.165884Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:27.166318Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.166585Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.166889Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.167283Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:27.167627Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.167941Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.168362Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.169095Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:27.169610Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.170188Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.170680Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.171312Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_sitegiant1\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:27.172143Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.172631Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.173726Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_sitegiant1/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.174411Z 0 [Warning] InnoDB: Ignoring tablespace `client_sitegiant1/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:27.175093Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.175488Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.175784Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.176163Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_thsa1\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:27.176484Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.176809Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.177217Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_thsa1/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.177859Z 0 [Warning] InnoDB: Ignoring tablespace `client_thsa1/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:27.178299Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.178552Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.178898Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.179294Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_thsa1\wp_comments.ibd' OS error: 103
2025-06-10T12:22:27.179693Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.180008Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.180508Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_thsa1/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.181092Z 0 [Warning] InnoDB: Ignoring tablespace `client_thsa1/wp_comments` because it could not be opened.
2025-06-10T12:22:27.181506Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.181808Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.182081Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.182466Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_thsa1\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:27.182818Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.183081Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.183496Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_thsa1/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.184178Z 0 [Warning] InnoDB: Ignoring tablespace `client_thsa1/wp_fbv` because it could not be opened.
2025-06-10T12:22:27.184546Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.184828Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.185100Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.185483Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_thsa1\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:27.185937Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.186219Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.186917Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_thsa1/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.187564Z 0 [Warning] InnoDB: Ignoring tablespace `client_thsa1/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:27.188057Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.188331Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.188606Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.189034Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_thsa1\wp_links.ibd' OS error: 103
2025-06-10T12:22:27.189375Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.189645Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.190098Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_thsa1/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.190634Z 0 [Warning] InnoDB: Ignoring tablespace `client_thsa1/wp_links` because it could not be opened.
2025-06-10T12:22:27.191151Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.191429Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.191777Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.192382Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_thsa1\wp_options.ibd' OS error: 103
2025-06-10T12:22:27.192718Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.193378Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.193823Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_thsa1/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.194530Z 0 [Warning] InnoDB: Ignoring tablespace `client_thsa1/wp_options` because it could not be opened.
2025-06-10T12:22:27.195004Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.195283Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.195561Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.195988Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_thsa1\wp_post_views.ibd' OS error: 103
2025-06-10T12:22:27.196327Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.196639Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.197158Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_thsa1/wp_post_views`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.197784Z 0 [Warning] InnoDB: Ignoring tablespace `client_thsa1/wp_post_views` because it could not be opened.
2025-06-10T12:22:27.198256Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.198519Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.198869Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.199242Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_thsa1\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:27.199559Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.200141Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.200582Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_thsa1/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.201256Z 0 [Warning] InnoDB: Ignoring tablespace `client_thsa1/wp_postmeta` because it could not be opened.
2025-06-10T12:22:27.201807Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.202189Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.202450Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.202861Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_thsa1\wp_posts.ibd' OS error: 103
2025-06-10T12:22:27.203157Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.203406Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.203918Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_thsa1/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.204438Z 0 [Warning] InnoDB: Ignoring tablespace `client_thsa1/wp_posts` because it could not be opened.
2025-06-10T12:22:27.204913Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.205167Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.205425Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.205943Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_thsa1\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:27.206269Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.206738Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.207334Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_thsa1/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.207949Z 0 [Warning] InnoDB: Ignoring tablespace `client_thsa1/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:27.208350Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.208670Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.208948Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.209413Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_thsa1\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:27.209827Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.210079Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.210471Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_thsa1/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.211110Z 0 [Warning] InnoDB: Ignoring tablespace `client_thsa1/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:27.211493Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.211838Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.212117Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.212757Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_thsa1\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:27.213269Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.213732Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.214127Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_thsa1/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.214758Z 0 [Warning] InnoDB: Ignoring tablespace `client_thsa1/wp_termmeta` because it could not be opened.
2025-06-10T12:22:27.215147Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.215399Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.215800Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.216161Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_thsa1\wp_terms.ibd' OS error: 103
2025-06-10T12:22:27.216458Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.216835Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.217273Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_thsa1/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.218080Z 0 [Warning] InnoDB: Ignoring tablespace `client_thsa1/wp_terms` because it could not be opened.
2025-06-10T12:22:27.218500Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.218841Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.219157Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.219623Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_thsa1\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:27.219964Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.220218Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.220713Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_thsa1/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.221306Z 0 [Warning] InnoDB: Ignoring tablespace `client_thsa1/wp_usermeta` because it could not be opened.
2025-06-10T12:22:27.221745Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.221995Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.222251Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.222859Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_thsa1\wp_users.ibd' OS error: 103
2025-06-10T12:22:27.223159Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.223450Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.223924Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_thsa1/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.224455Z 0 [Warning] InnoDB: Ignoring tablespace `client_thsa1/wp_users` because it could not be opened.
2025-06-10T12:22:27.224904Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.225364Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.225736Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.226186Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_thsa1\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:27.226582Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.226923Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.227310Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_thsa1/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.227957Z 0 [Warning] InnoDB: Ignoring tablespace `client_thsa1/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:27.228397Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.228732Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.228994Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.229350Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_thsa1\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:27.229744Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.229988Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.230368Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_thsa1/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.230982Z 0 [Warning] InnoDB: Ignoring tablespace `client_thsa1/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:27.231517Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.231800Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.232053Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.232407Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_thsa1\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:27.232987Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.233273Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.233792Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_thsa1/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.234410Z 0 [Warning] InnoDB: Ignoring tablespace `client_thsa1/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:27.234934Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.235178Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.235430Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.235892Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_thsa1\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:27.236227Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.236522Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.236939Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_thsa1/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.237559Z 0 [Warning] InnoDB: Ignoring tablespace `client_thsa1/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:27.237998Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.238262Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.238745Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.239335Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_thsa1\wp_yoast_indexable.ibd' OS error: 103
2025-06-10T12:22:27.239769Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.240021Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.240412Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_thsa1/wp_yoast_indexable`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.241414Z 0 [Warning] InnoDB: Ignoring tablespace `client_thsa1/wp_yoast_indexable` because it could not be opened.
2025-06-10T12:22:27.241950Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.242433Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.242728Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.243398Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_thsa1\wp_yoast_indexable_hierarchy.ibd' OS error: 103
2025-06-10T12:22:27.243783Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.244164Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.244631Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_thsa1/wp_yoast_indexable_hierarchy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.245357Z 0 [Warning] InnoDB: Ignoring tablespace `client_thsa1/wp_yoast_indexable_hierarchy` because it could not be opened.
2025-06-10T12:22:27.245820Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.246163Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.246704Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.247584Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_thsa1\wp_yoast_migrations.ibd' OS error: 103
2025-06-10T12:22:27.248313Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.248764Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.249258Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_thsa1/wp_yoast_migrations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.249831Z 0 [Warning] InnoDB: Ignoring tablespace `client_thsa1/wp_yoast_migrations` because it could not be opened.
2025-06-10T12:22:27.250541Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.250988Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.251282Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.251686Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_thsa1\wp_yoast_primary_term.ibd' OS error: 103
2025-06-10T12:22:27.252153Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.252434Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.252979Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_thsa1/wp_yoast_primary_term`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.253532Z 0 [Warning] InnoDB: Ignoring tablespace `client_thsa1/wp_yoast_primary_term` because it could not be opened.
2025-06-10T12:22:27.254069Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.254356Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.254845Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.255344Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_thsa1\wp_yoast_prominent_words.ibd' OS error: 103
2025-06-10T12:22:27.255685Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.256028Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.256500Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_thsa1/wp_yoast_prominent_words`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.257193Z 0 [Warning] InnoDB: Ignoring tablespace `client_thsa1/wp_yoast_prominent_words` because it could not be opened.
2025-06-10T12:22:27.257603Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.257914Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.258193Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.258559Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_thsa1\wp_yoast_seo_links.ibd' OS error: 103
2025-06-10T12:22:27.258944Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.259258Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.259719Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_thsa1/wp_yoast_seo_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.260433Z 0 [Warning] InnoDB: Ignoring tablespace `client_thsa1/wp_yoast_seo_links` because it could not be opened.
2025-06-10T12:22:27.260811Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.261173Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.261486Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.261938Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_thsa2\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:27.262246Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.262498Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.263039Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_thsa2/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.263580Z 0 [Warning] InnoDB: Ignoring tablespace `client_thsa2/wp_fbv` because it could not be opened.
2025-06-10T12:22:27.264002Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.264273Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.264532Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.264976Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_thsa2\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:27.265312Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.265565Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.266066Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_thsa2/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.266657Z 0 [Warning] InnoDB: Ignoring tablespace `client_thsa2/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:27.267119Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.267373Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.267817Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.268208Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_thsa2\wp_post_views.ibd' OS error: 103
2025-06-10T12:22:27.268521Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.268777Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.269320Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_thsa2/wp_post_views`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.269923Z 0 [Warning] InnoDB: Ignoring tablespace `client_thsa2/wp_post_views` because it could not be opened.
2025-06-10T12:22:27.270319Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.270573Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.270937Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.271413Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_thsa2\wp_revslider_css.ibd' OS error: 103
2025-06-10T12:22:27.271860Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.272250Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.272849Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_thsa2/wp_revslider_css`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.273447Z 0 [Warning] InnoDB: Ignoring tablespace `client_thsa2/wp_revslider_css` because it could not be opened.
2025-06-10T12:22:27.273872Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.274279Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.274648Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.275113Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_thsa2\wp_revslider_css_bkp.ibd' OS error: 103
2025-06-10T12:22:27.275435Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.275684Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.276232Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_thsa2/wp_revslider_css_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.276769Z 0 [Warning] InnoDB: Ignoring tablespace `client_thsa2/wp_revslider_css_bkp` because it could not be opened.
2025-06-10T12:22:27.277316Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.277573Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.278019Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.278442Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_thsa2\wp_revslider_layer_animations.ibd' OS error: 103
2025-06-10T12:22:27.278905Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.279299Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.279713Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_thsa2/wp_revslider_layer_animations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.280600Z 0 [Warning] InnoDB: Ignoring tablespace `client_thsa2/wp_revslider_layer_animations` because it could not be opened.
2025-06-10T12:22:27.281453Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.281776Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.282209Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.282631Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_thsa2\wp_revslider_layer_animations_bkp.ibd' OS error: 103
2025-06-10T12:22:27.283084Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.283346Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.283754Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_thsa2/wp_revslider_layer_animations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.284413Z 0 [Warning] InnoDB: Ignoring tablespace `client_thsa2/wp_revslider_layer_animations_bkp` because it could not be opened.
2025-06-10T12:22:27.284941Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.285229Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.285496Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.285932Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_thsa2\wp_revslider_navigations.ibd' OS error: 103
2025-06-10T12:22:27.286297Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.286560Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.287057Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_thsa2/wp_revslider_navigations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.287665Z 0 [Warning] InnoDB: Ignoring tablespace `client_thsa2/wp_revslider_navigations` because it could not be opened.
2025-06-10T12:22:27.288235Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.288633Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.289219Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.289620Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_thsa2\wp_revslider_navigations_bkp.ibd' OS error: 103
2025-06-10T12:22:27.290068Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.290314Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.290697Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_thsa2/wp_revslider_navigations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.291354Z 0 [Warning] InnoDB: Ignoring tablespace `client_thsa2/wp_revslider_navigations_bkp` because it could not be opened.
2025-06-10T12:22:27.291760Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.292316Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.292685Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.293241Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_thsa2\wp_revslider_sliders.ibd' OS error: 103
2025-06-10T12:22:27.293596Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.293921Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.294328Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_thsa2/wp_revslider_sliders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.295262Z 0 [Warning] InnoDB: Ignoring tablespace `client_thsa2/wp_revslider_sliders` because it could not be opened.
2025-06-10T12:22:27.295839Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.296127Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.296386Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.296804Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_thsa2\wp_revslider_sliders_bkp.ibd' OS error: 103
2025-06-10T12:22:27.297167Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.297421Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.297919Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_thsa2/wp_revslider_sliders_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.298514Z 0 [Warning] InnoDB: Ignoring tablespace `client_thsa2/wp_revslider_sliders_bkp` because it could not be opened.
2025-06-10T12:22:27.299072Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.299358Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.299616Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.300058Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_thsa2\wp_revslider_slides.ibd' OS error: 103
2025-06-10T12:22:27.300384Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.300670Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.301197Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_thsa2/wp_revslider_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.301851Z 0 [Warning] InnoDB: Ignoring tablespace `client_thsa2/wp_revslider_slides` because it could not be opened.
2025-06-10T12:22:27.302270Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.302533Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.302851Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.303237Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_thsa2\wp_revslider_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:27.303580Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.303937Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.305039Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_thsa2/wp_revslider_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.306256Z 0 [Warning] InnoDB: Ignoring tablespace `client_thsa2/wp_revslider_slides_bkp` because it could not be opened.
2025-06-10T12:22:27.306710Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.307009Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.307303Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.307683Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_thsa2\wp_revslider_static_slides.ibd' OS error: 103
2025-06-10T12:22:27.308133Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.308409Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.308959Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_thsa2/wp_revslider_static_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.309561Z 0 [Warning] InnoDB: Ignoring tablespace `client_thsa2/wp_revslider_static_slides` because it could not be opened.
2025-06-10T12:22:27.310048Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.310316Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.310584Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.311174Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_thsa2\wp_revslider_static_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:27.311534Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.311936Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.312356Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_thsa2/wp_revslider_static_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.313060Z 0 [Warning] InnoDB: Ignoring tablespace `client_thsa2/wp_revslider_static_slides_bkp` because it could not be opened.
2025-06-10T12:22:27.313616Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.314064Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.314417Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.314914Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_thsa2\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:27.315276Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.315573Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.316140Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_thsa2/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.316724Z 0 [Warning] InnoDB: Ignoring tablespace `client_thsa2/wp_usermeta` because it could not be opened.
2025-06-10T12:22:27.317124Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.317388Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.317658Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.318098Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_thsa2\wp_users.ibd' OS error: 103
2025-06-10T12:22:27.318411Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.318672Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.319149Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_thsa2/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.319746Z 0 [Warning] InnoDB: Ignoring tablespace `client_thsa2/wp_users` because it could not be opened.
2025-06-10T12:22:27.320112Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.320376Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.320645Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.321082Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_thsa2\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:27.321432Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.321740Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.322223Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_thsa2/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.322876Z 0 [Warning] InnoDB: Ignoring tablespace `client_thsa2/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:27.323307Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.323557Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.323863Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.324228Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_thsa2\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:27.324539Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.324883Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.325275Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_thsa2/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.325909Z 0 [Warning] InnoDB: Ignoring tablespace `client_thsa2/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:27.326265Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.326515Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.326873Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.327243Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_thsa2\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:27.327555Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.328115Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.328597Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_thsa2/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.329236Z 0 [Warning] InnoDB: Ignoring tablespace `client_thsa2/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:27.329615Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.329943Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.330384Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.331060Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_thsa2\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:27.331424Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.331738Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.332233Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_thsa2/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.332968Z 0 [Warning] InnoDB: Ignoring tablespace `client_thsa2/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:27.334045Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.334390Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.334683Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.335185Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_actionscheduler_actions.ibd' OS error: 103
2025-06-10T12:22:27.335538Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.335873Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.336570Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_actionscheduler_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.337279Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_actionscheduler_actions` because it could not be opened.
2025-06-10T12:22:27.338088Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.338360Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.338791Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.339203Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_actionscheduler_claims.ibd' OS error: 103
2025-06-10T12:22:27.339782Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.340063Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.340480Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_actionscheduler_claims`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.341164Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_actionscheduler_claims` because it could not be opened.
2025-06-10T12:22:27.341624Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.341932Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.342309Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.342726Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_actionscheduler_groups.ibd' OS error: 103
2025-06-10T12:22:27.343098Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.343367Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.344266Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_actionscheduler_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.345059Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_actionscheduler_groups` because it could not be opened.
2025-06-10T12:22:27.345641Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.346038Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.346453Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.346923Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_actionscheduler_logs.ibd' OS error: 103
2025-06-10T12:22:27.347373Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.347622Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.348097Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_actionscheduler_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.348639Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_actionscheduler_logs` because it could not be opened.
2025-06-10T12:22:27.349350Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.349601Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.350185Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.350563Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:27.350974Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.351229Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.351619Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.352238Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:27.352616Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.353009Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.353313Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.353729Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_comments.ibd' OS error: 103
2025-06-10T12:22:27.354056Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.354305Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.354744Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.355295Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_comments` because it could not be opened.
2025-06-10T12:22:27.355699Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.356007Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.356268Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.356628Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_frontend_post_form_meta.ibd' OS error: 103
2025-06-10T12:22:27.357085Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.357334Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.357778Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_frontend_post_form_meta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.358348Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_frontend_post_form_meta` because it could not be opened.
2025-06-10T12:22:27.358821Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.359090Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.359342Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.359786Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_frontend_post_forms.ibd' OS error: 103
2025-06-10T12:22:27.360134Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.360385Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.360837Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_frontend_post_forms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.361396Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_frontend_post_forms` because it could not be opened.
2025-06-10T12:22:27.362040Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.362357Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.362621Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.363060Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_links.ibd' OS error: 103
2025-06-10T12:22:27.363365Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.363612Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.364104Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.364796Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_links` because it could not be opened.
2025-06-10T12:22:27.365321Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.365571Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.366022Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.366374Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_notification_logs.ibd' OS error: 103
2025-06-10T12:22:27.366761Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.367078Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.367463Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_notification_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.368265Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_notification_logs` because it could not be opened.
2025-06-10T12:22:27.369096Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.369372Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.369756Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.370154Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_options.ibd' OS error: 103
2025-06-10T12:22:27.370774Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.371124Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.371542Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.372127Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_options` because it could not be opened.
2025-06-10T12:22:27.372589Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.372899Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.373182Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.373604Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_post_views.ibd' OS error: 103
2025-06-10T12:22:27.373945Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.374213Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.374680Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_post_views`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.375256Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_post_views` because it could not be opened.
2025-06-10T12:22:27.375748Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.376016Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.376412Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.376939Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:27.377272Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.377573Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.378104Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.378827Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_postmeta` because it could not be opened.
2025-06-10T12:22:27.379355Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.379850Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.380312Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.380865Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_posts.ibd' OS error: 103
2025-06-10T12:22:27.381202Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.381463Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.382058Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.382697Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_posts` because it could not be opened.
2025-06-10T12:22:27.383115Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.383815Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.384109Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.384488Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_revslider_css.ibd' OS error: 103
2025-06-10T12:22:27.384906Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.385162Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.385644Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_revslider_css`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.386440Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_revslider_css` because it could not be opened.
2025-06-10T12:22:27.387086Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.387345Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.387697Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.388083Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_revslider_css_bkp.ibd' OS error: 103
2025-06-10T12:22:27.388431Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.388761Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.389175Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_revslider_css_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.389821Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_revslider_css_bkp` because it could not be opened.
2025-06-10T12:22:27.390444Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.390761Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.391044Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.391444Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_revslider_layer_animations.ibd' OS error: 103
2025-06-10T12:22:27.391848Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.392125Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.392586Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_revslider_layer_animations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.393219Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_revslider_layer_animations` because it could not be opened.
2025-06-10T12:22:27.393738Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.394001Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.394317Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.394736Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_revslider_layer_animations_bkp.ibd' OS error: 103
2025-06-10T12:22:27.395121Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.395389Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.395889Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_revslider_layer_animations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.396644Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_revslider_layer_animations_bkp` because it could not be opened.
2025-06-10T12:22:27.397354Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.397698Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.397962Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.398330Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_revslider_navigations.ibd' OS error: 103
2025-06-10T12:22:27.398770Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.399025Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.399423Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_revslider_navigations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.400095Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_revslider_navigations` because it could not be opened.
2025-06-10T12:22:27.401757Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.402069Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.402346Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.402754Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_revslider_navigations_bkp.ibd' OS error: 103
2025-06-10T12:22:27.403150Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.403416Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.403849Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_revslider_navigations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.404696Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_revslider_navigations_bkp` because it could not be opened.
2025-06-10T12:22:27.405290Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.405618Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.405899Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.406438Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_revslider_sliders.ibd' OS error: 103
2025-06-10T12:22:27.406974Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.407270Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.407746Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_revslider_sliders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.408322Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_revslider_sliders` because it could not be opened.
2025-06-10T12:22:27.408830Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.409091Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.409357Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.409839Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_revslider_sliders_bkp.ibd' OS error: 103
2025-06-10T12:22:27.410205Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.410506Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.411010Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_revslider_sliders_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.411682Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_revslider_sliders_bkp` because it could not be opened.
2025-06-10T12:22:27.412694Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.413076Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.413347Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.413838Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_revslider_slides.ibd' OS error: 103
2025-06-10T12:22:27.414174Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.414426Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.415044Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_revslider_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.415761Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_revslider_slides` because it could not be opened.
2025-06-10T12:22:27.416274Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.416690Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.416992Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.417559Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_revslider_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:27.417964Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.418216Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.418705Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_revslider_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.419370Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_revslider_slides_bkp` because it could not be opened.
2025-06-10T12:22:27.419904Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.420180Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.420494Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.420882Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_revslider_static_slides.ibd' OS error: 103
2025-06-10T12:22:27.421239Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.421546Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.421961Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_revslider_static_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.422602Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_revslider_static_slides` because it could not be opened.
2025-06-10T12:22:27.423018Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.423282Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.423598Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.423980Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_revslider_static_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:27.424349Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.424654Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.425286Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_revslider_static_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.425922Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_revslider_static_slides_bkp` because it could not be opened.
2025-06-10T12:22:27.426370Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.426702Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.426975Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.427366Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:27.427785Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.428048Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.428499Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.429093Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:27.429607Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.429879Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.430150Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.430599Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:27.430929Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.431180Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.431659Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.432440Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:27.434153Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.434425Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.434909Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.435298Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:27.435633Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.435921Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.436492Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.437147Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_termmeta` because it could not be opened.
2025-06-10T12:22:27.437587Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.437864Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.438264Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.438676Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_terms.ibd' OS error: 103
2025-06-10T12:22:27.439113Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.439390Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.439813Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.440479Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_terms` because it could not be opened.
2025-06-10T12:22:27.440956Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.441240Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.441520Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.441951Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_um_metadata.ibd' OS error: 103
2025-06-10T12:22:27.442307Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.442583Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.443068Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_um_metadata`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.443640Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_um_metadata` because it could not be opened.
2025-06-10T12:22:27.444097Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.444363Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.444633Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.445088Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:27.445486Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.445753Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.446255Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.446807Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_usermeta` because it could not be opened.
2025-06-10T12:22:27.447258Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.447520Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.447786Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.448231Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_users.ibd' OS error: 103
2025-06-10T12:22:27.448546Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.448801Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.449282Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.449824Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_users` because it could not be opened.
2025-06-10T12:22:27.450246Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.450505Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.450801Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.451284Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_wc_admin_note_actions.ibd' OS error: 103
2025-06-10T12:22:27.451694Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.451996Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.452411Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_wc_admin_note_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.453037Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_wc_admin_note_actions` because it could not be opened.
2025-06-10T12:22:27.453460Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.453730Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.454032Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.454414Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_wc_admin_notes.ibd' OS error: 103
2025-06-10T12:22:27.454754Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.455034Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.455521Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_wc_admin_notes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.456152Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_wc_admin_notes` because it could not be opened.
2025-06-10T12:22:27.456598Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.456885Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.457198Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.457623Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_wc_category_lookup.ibd' OS error: 103
2025-06-10T12:22:27.458021Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.458293Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.458711Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_wc_category_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.459454Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_wc_category_lookup` because it could not be opened.
2025-06-10T12:22:27.459923Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.460198Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.460478Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.460922Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_wc_customer_lookup.ibd' OS error: 103
2025-06-10T12:22:27.461293Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.461562Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.462046Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_wc_customer_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.462626Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_wc_customer_lookup` because it could not be opened.
2025-06-10T12:22:27.463116Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.463555Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.463869Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.464265Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_wc_download_log.ibd' OS error: 103
2025-06-10T12:22:27.464606Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.465038Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.465569Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_wc_download_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.466344Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_wc_download_log` because it could not be opened.
2025-06-10T12:22:27.466868Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.467386Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.467737Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.468313Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_wc_order_coupon_lookup.ibd' OS error: 103
2025-06-10T12:22:27.468669Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.469028Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.469428Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_wc_order_coupon_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.470089Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_wc_order_coupon_lookup` because it could not be opened.
2025-06-10T12:22:27.470553Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.471130Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.471566Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.471978Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_wc_order_product_lookup.ibd' OS error: 103
2025-06-10T12:22:27.472342Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.472606Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.473109Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_wc_order_product_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.473709Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_wc_order_product_lookup` because it could not be opened.
2025-06-10T12:22:27.474211Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.474468Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.474731Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.475194Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_wc_order_stats.ibd' OS error: 103
2025-06-10T12:22:27.475525Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.475772Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.476268Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_wc_order_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.477004Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_wc_order_stats` because it could not be opened.
2025-06-10T12:22:27.477473Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.477737Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.478132Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.478554Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_wc_order_tax_lookup.ibd' OS error: 103
2025-06-10T12:22:27.479021Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.479313Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.479839Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_wc_order_tax_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.480790Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_wc_order_tax_lookup` because it could not be opened.
2025-06-10T12:22:27.481350Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.481716Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.481989Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.482869Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_wc_product_meta_lookup.ibd' OS error: 103
2025-06-10T12:22:27.483237Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.483508Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.484365Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_wc_product_meta_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.485252Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_wc_product_meta_lookup` because it could not be opened.
2025-06-10T12:22:27.486035Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.486367Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.486722Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.487280Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_wc_reserved_stock.ibd' OS error: 103
2025-06-10T12:22:27.487698Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.488123Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.488605Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_wc_reserved_stock`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.489234Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_wc_reserved_stock` because it could not be opened.
2025-06-10T12:22:27.489715Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.490090Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.490439Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.490904Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_wc_tax_rate_classes.ibd' OS error: 103
2025-06-10T12:22:27.491286Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.491573Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.492120Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_wc_tax_rate_classes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.492897Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_wc_tax_rate_classes` because it could not be opened.
2025-06-10T12:22:27.493457Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.493833Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.494169Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.494595Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_wc_webhooks.ibd' OS error: 103
2025-06-10T12:22:27.495004Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.495286Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.495681Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_wc_webhooks`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.496357Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_wc_webhooks` because it could not be opened.
2025-06-10T12:22:27.496773Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.497122Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.497383Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.497749Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_woocommerce_api_keys.ibd' OS error: 103
2025-06-10T12:22:27.498213Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.498620Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.499127Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_woocommerce_api_keys`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.499733Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_woocommerce_api_keys` because it could not be opened.
2025-06-10T12:22:27.500243Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.500532Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.500864Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.501328Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_woocommerce_attribute_taxonomies.ibd' OS error: 103
2025-06-10T12:22:27.501701Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.502163Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.502555Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_woocommerce_attribute_taxonomies`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.503298Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_woocommerce_attribute_taxonomies` because it could not be opened.
2025-06-10T12:22:27.503842Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.504127Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.504386Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.504753Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_woocommerce_downloadable_product_permissions.ibd' OS error: 103
2025-06-10T12:22:27.505267Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.505518Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.506014Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_woocommerce_downloadable_product_permissions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.506692Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_woocommerce_downloadable_product_permissions` because it could not be opened.
2025-06-10T12:22:27.507187Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.507555Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.507935Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.508317Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_woocommerce_log.ibd' OS error: 103
2025-06-10T12:22:27.508816Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.509215Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.509632Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_woocommerce_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.510314Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_woocommerce_log` because it could not be opened.
2025-06-10T12:22:27.510739Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.511097Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.511352Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.511705Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_woocommerce_order_itemmeta.ibd' OS error: 103
2025-06-10T12:22:27.512361Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.512610Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.513340Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_woocommerce_order_itemmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.514743Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_woocommerce_order_itemmeta` because it could not be opened.
2025-06-10T12:22:27.515373Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.515644Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.515912Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.516327Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_woocommerce_order_items.ibd' OS error: 103
2025-06-10T12:22:27.516685Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.516944Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.517418Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_woocommerce_order_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.518068Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_woocommerce_order_items` because it could not be opened.
2025-06-10T12:22:27.518545Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.518810Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.519151Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.519546Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_woocommerce_payment_tokenmeta.ibd' OS error: 103
2025-06-10T12:22:27.519924Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.520265Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.520687Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_woocommerce_payment_tokenmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.521407Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_woocommerce_payment_tokenmeta` because it could not be opened.
2025-06-10T12:22:27.521926Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.522434Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.522784Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.523241Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_woocommerce_payment_tokens.ibd' OS error: 103
2025-06-10T12:22:27.523584Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.523861Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.524333Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_woocommerce_payment_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.524899Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_woocommerce_payment_tokens` because it could not be opened.
2025-06-10T12:22:27.525438Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.525688Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.526042Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.526464Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_woocommerce_sessions.ibd' OS error: 103
2025-06-10T12:22:27.526815Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.527212Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.527605Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_woocommerce_sessions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.528365Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_woocommerce_sessions` because it could not be opened.
2025-06-10T12:22:27.528802Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.529213Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.529556Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.529916Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_woocommerce_shipping_zone_locations.ibd' OS error: 103
2025-06-10T12:22:27.530696Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.531356Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.531999Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_woocommerce_shipping_zone_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.533003Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_woocommerce_shipping_zone_locations` because it could not be opened.
2025-06-10T12:22:27.533727Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.534185Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.534602Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.535280Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_woocommerce_shipping_zone_methods.ibd' OS error: 103
2025-06-10T12:22:27.535820Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.536261Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.536664Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_woocommerce_shipping_zone_methods`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.537322Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_woocommerce_shipping_zone_methods` because it could not be opened.
2025-06-10T12:22:27.537762Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.538081Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.538373Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.538846Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_woocommerce_shipping_zones.ibd' OS error: 103
2025-06-10T12:22:27.539319Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.539575Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.540063Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_woocommerce_shipping_zones`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.540853Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_woocommerce_shipping_zones` because it could not be opened.
2025-06-10T12:22:27.541474Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.541731Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.542062Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.542561Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_woocommerce_tax_rate_locations.ibd' OS error: 103
2025-06-10T12:22:27.543071Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.543406Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.543985Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_woocommerce_tax_rate_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.544803Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_woocommerce_tax_rate_locations` because it could not be opened.
2025-06-10T12:22:27.545399Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.545665Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.546041Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.546505Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_woocommerce_tax_rates.ibd' OS error: 103
2025-06-10T12:22:27.547080Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.547368Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.547845Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_woocommerce_tax_rates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.548555Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_woocommerce_tax_rates` because it could not be opened.
2025-06-10T12:22:27.549050Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.549325Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.549600Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.550021Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_wpuf_subscribers.ibd' OS error: 103
2025-06-10T12:22:27.550376Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.550827Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.551404Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_wpuf_subscribers`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.552093Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_wpuf_subscribers` because it could not be opened.
2025-06-10T12:22:27.552575Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.552869Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.553200Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.553605Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_wpuf_transaction.ibd' OS error: 103
2025-06-10T12:22:27.554016Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.554336Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.554770Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_wpuf_transaction`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.555405Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_wpuf_transaction` because it could not be opened.
2025-06-10T12:22:27.555846Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.556147Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.556425Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.556817Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:27.557347Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.557624Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.558096Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.558728Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:27.559242Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.559516Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.559792Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.560220Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:27.560565Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.560834Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.561290Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.561888Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:27.562420Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.562781Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.563161Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.563727Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:27.564419Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.564717Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.565360Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.566241Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:27.566713Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.567027Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.567287Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.567654Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh1\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:27.568136Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.568455Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.568839Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh1/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.569559Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh1/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:27.570057Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.570385Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.570640Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.571098Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_actionscheduler_actions.ibd' OS error: 103
2025-06-10T12:22:27.571515Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.571799Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.572338Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_actionscheduler_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.573130Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_actionscheduler_actions` because it could not be opened.
2025-06-10T12:22:27.573744Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.574231Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.574497Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.574858Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_actionscheduler_claims.ibd' OS error: 103
2025-06-10T12:22:27.575287Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.575533Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.575958Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_actionscheduler_claims`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.576906Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_actionscheduler_claims` because it could not be opened.
2025-06-10T12:22:27.577367Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.577696Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.578398Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.579019Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_actionscheduler_groups.ibd' OS error: 103
2025-06-10T12:22:27.579389Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.579673Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.580434Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_actionscheduler_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.581178Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_actionscheduler_groups` because it could not be opened.
2025-06-10T12:22:27.581743Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.582056Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.582319Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.582742Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_actionscheduler_logs.ibd' OS error: 103
2025-06-10T12:22:27.583137Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.583396Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.583968Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_actionscheduler_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.584580Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_actionscheduler_logs` because it could not be opened.
2025-06-10T12:22:27.585120Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.585498Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.585802Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.586185Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:27.586510Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.586845Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.587260Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.587864Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:27.588278Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.588542Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.588839Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.589220Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_comments.ibd' OS error: 103
2025-06-10T12:22:27.589548Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.589930Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.590342Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.590936Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_comments` because it could not be opened.
2025-06-10T12:22:27.591320Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.591602Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.592098Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.592500Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_links.ibd' OS error: 103
2025-06-10T12:22:27.592859Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.593128Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.593521Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.594125Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_links` because it could not be opened.
2025-06-10T12:22:27.594509Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.594925Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.595243Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.595760Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_notification_logs.ibd' OS error: 103
2025-06-10T12:22:27.596146Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.596409Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.596887Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_notification_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.597475Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_notification_logs` because it could not be opened.
2025-06-10T12:22:27.598048Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.598326Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.598598Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.599163Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_options.ibd' OS error: 103
2025-06-10T12:22:27.599480Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.599868Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.600270Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.600890Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_options` because it could not be opened.
2025-06-10T12:22:27.601294Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.601544Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.601932Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.602333Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_post_views.ibd' OS error: 103
2025-06-10T12:22:27.602851Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.603105Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.603532Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_post_views`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.604167Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_post_views` because it could not be opened.
2025-06-10T12:22:27.604562Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.604918Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.605227Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.605611Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:27.606003Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.606267Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.606920Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.607490Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_postmeta` because it could not be opened.
2025-06-10T12:22:27.607982Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.608248Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.608517Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.609093Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_posts.ibd' OS error: 103
2025-06-10T12:22:27.609450Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.609710Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.610221Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.611243Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_posts` because it could not be opened.
2025-06-10T12:22:27.611773Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.612159Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.612480Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.612939Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_revslider_css.ibd' OS error: 103
2025-06-10T12:22:27.613315Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.613586Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.614145Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_revslider_css`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.614773Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_revslider_css` because it could not be opened.
2025-06-10T12:22:27.615330Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.615641Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.616057Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.616447Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_revslider_css_bkp.ibd' OS error: 103
2025-06-10T12:22:27.616790Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.617240Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.617642Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_revslider_css_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.618358Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_revslider_css_bkp` because it could not be opened.
2025-06-10T12:22:27.618983Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.619292Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.619567Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.620074Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_revslider_layer_animations.ibd' OS error: 103
2025-06-10T12:22:27.620450Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.620714Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.621506Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_revslider_layer_animations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.622435Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_revslider_layer_animations` because it could not be opened.
2025-06-10T12:22:27.622998Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.623308Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.623584Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.624031Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_revslider_layer_animations_bkp.ibd' OS error: 103
2025-06-10T12:22:27.624392Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.624644Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.625126Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_revslider_layer_animations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.625931Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_revslider_layer_animations_bkp` because it could not be opened.
2025-06-10T12:22:27.626408Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.626677Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.627006Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.627380Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_revslider_navigations.ibd' OS error: 103
2025-06-10T12:22:27.627721Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.628037Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.628432Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_revslider_navigations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.629127Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_revslider_navigations` because it could not be opened.
2025-06-10T12:22:27.629587Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.629897Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.630172Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.630567Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_revslider_navigations_bkp.ibd' OS error: 103
2025-06-10T12:22:27.630996Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.631250Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.631649Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_revslider_navigations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.632350Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_revslider_navigations_bkp` because it could not be opened.
2025-06-10T12:22:27.632991Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.633355Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.633654Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.634122Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_revslider_sliders.ibd' OS error: 103
2025-06-10T12:22:27.634473Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.634735Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.635237Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_revslider_sliders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.635877Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_revslider_sliders` because it could not be opened.
2025-06-10T12:22:27.636360Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.636744Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.637144Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.637567Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_revslider_sliders_bkp.ibd' OS error: 103
2025-06-10T12:22:27.638013Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.638264Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.638817Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_revslider_sliders_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.639678Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_revslider_sliders_bkp` because it could not be opened.
2025-06-10T12:22:27.640325Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.640838Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.641386Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.641944Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_revslider_slides.ibd' OS error: 103
2025-06-10T12:22:27.642485Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.642795Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.643232Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_revslider_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.643866Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_revslider_slides` because it could not be opened.
2025-06-10T12:22:27.644337Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.644605Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.644894Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.645272Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_revslider_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:27.645626Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.645914Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.646334Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_revslider_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.647168Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_revslider_slides_bkp` because it could not be opened.
2025-06-10T12:22:27.647737Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.648028Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.648319Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.648743Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_revslider_static_slides.ibd' OS error: 103
2025-06-10T12:22:27.649132Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.649411Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.649979Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_revslider_static_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.650696Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_revslider_static_slides` because it could not be opened.
2025-06-10T12:22:27.651229Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.651560Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.651988Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.652389Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_revslider_static_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:27.652820Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.653088Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.653515Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_revslider_static_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.654349Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_revslider_static_slides_bkp` because it could not be opened.
2025-06-10T12:22:27.654989Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.655493Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.656012Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.656702Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:27.657124Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.657390Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.657911Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.658504Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:27.659005Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.659275Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.659549Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.660002Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:27.660345Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.660609Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.661176Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.661796Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:27.662215Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.662483Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.662803Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.663188Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:27.663510Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.663799Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.664220Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.664812Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_termmeta` because it could not be opened.
2025-06-10T12:22:27.665190Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.665454Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.665745Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.666132Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_terms.ibd' OS error: 103
2025-06-10T12:22:27.666455Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.666784Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.667339Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.667985Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_terms` because it could not be opened.
2025-06-10T12:22:27.668396Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.668708Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.668987Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.669358Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:27.669828Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.670084Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.670486Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.671173Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_usermeta` because it could not be opened.
2025-06-10T12:22:27.671610Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.671903Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.672179Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.672566Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_users.ibd' OS error: 103
2025-06-10T12:22:27.673108Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.673378Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.673830Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.674400Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_users` because it could not be opened.
2025-06-10T12:22:27.674820Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.675091Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.675366Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.675788Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_wc_admin_note_actions.ibd' OS error: 103
2025-06-10T12:22:27.676144Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.676407Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.676854Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_wc_admin_note_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.677459Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_wc_admin_note_actions` because it could not be opened.
2025-06-10T12:22:27.677914Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.678183Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.678507Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.678963Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_wc_admin_notes.ibd' OS error: 103
2025-06-10T12:22:27.679328Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.679627Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.680124Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_wc_admin_notes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.680714Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_wc_admin_notes` because it could not be opened.
2025-06-10T12:22:27.681114Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.681372Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.681805Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.682190Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_wc_category_lookup.ibd' OS error: 103
2025-06-10T12:22:27.682531Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.682884Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.683282Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_wc_category_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.683910Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_wc_category_lookup` because it could not be opened.
2025-06-10T12:22:27.684352Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.684765Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.685083Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.685515Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_wc_customer_lookup.ibd' OS error: 103
2025-06-10T12:22:27.685943Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.686303Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.687114Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_wc_customer_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.687976Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_wc_customer_lookup` because it could not be opened.
2025-06-10T12:22:27.688563Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.688822Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.689550Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.690475Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_wc_download_log.ibd' OS error: 103
2025-06-10T12:22:27.690869Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.691135Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.691663Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_wc_download_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.692448Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_wc_download_log` because it could not be opened.
2025-06-10T12:22:27.692956Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.693222Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.693566Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.693991Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_wc_order_coupon_lookup.ibd' OS error: 103
2025-06-10T12:22:27.694361Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.694933Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.695401Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_wc_order_coupon_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.696098Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_wc_order_coupon_lookup` because it could not be opened.
2025-06-10T12:22:27.696605Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.696970Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.697248Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.697629Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_wc_order_product_lookup.ibd' OS error: 103
2025-06-10T12:22:27.698100Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.698385Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.698971Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_wc_order_product_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.700309Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_wc_order_product_lookup` because it could not be opened.
2025-06-10T12:22:27.701065Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.701482Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.701851Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.702344Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_wc_order_stats.ibd' OS error: 103
2025-06-10T12:22:27.702705Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.702977Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.703434Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_wc_order_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.704028Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_wc_order_stats` because it could not be opened.
2025-06-10T12:22:27.704493Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.704766Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.705150Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.705700Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_wc_order_tax_lookup.ibd' OS error: 103
2025-06-10T12:22:27.706096Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.706403Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.706829Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_wc_order_tax_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.707515Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_wc_order_tax_lookup` because it could not be opened.
2025-06-10T12:22:27.707933Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.708197Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.708516Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.708908Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_wc_product_meta_lookup.ibd' OS error: 103
2025-06-10T12:22:27.709302Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.709578Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.709982Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_wc_product_meta_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.710662Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_wc_product_meta_lookup` because it could not be opened.
2025-06-10T12:22:27.711081Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.711400Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.711664Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.712072Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_wc_reserved_stock.ibd' OS error: 103
2025-06-10T12:22:27.712493Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.712751Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.713173Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_wc_reserved_stock`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.713832Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_wc_reserved_stock` because it could not be opened.
2025-06-10T12:22:27.714262Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.714542Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.714821Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.715223Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_wc_tax_rate_classes.ibd' OS error: 103
2025-06-10T12:22:27.715627Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.715940Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.716440Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_wc_tax_rate_classes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.717123Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_wc_tax_rate_classes` because it could not be opened.
2025-06-10T12:22:27.717789Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.718053Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.718384Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.718756Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_wc_webhooks.ibd' OS error: 103
2025-06-10T12:22:27.719079Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.719442Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.719938Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_wc_webhooks`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.720839Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_wc_webhooks` because it could not be opened.
2025-06-10T12:22:27.721322Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.721627Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.721909Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.722390Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_woocommerce_api_keys.ibd' OS error: 103
2025-06-10T12:22:27.722798Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.723468Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.723940Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_woocommerce_api_keys`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.724575Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_woocommerce_api_keys` because it could not be opened.
2025-06-10T12:22:27.725098Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.725392Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.725667Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.726093Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_woocommerce_attribute_taxonomies.ibd' OS error: 103
2025-06-10T12:22:27.726478Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.726749Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.727196Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_woocommerce_attribute_taxonomies`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.727823Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_woocommerce_attribute_taxonomies` because it could not be opened.
2025-06-10T12:22:27.728362Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.728641Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.728952Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.729348Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_woocommerce_downloadable_product_permissions.ibd' OS error: 103
2025-06-10T12:22:27.729764Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.730105Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.730545Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_woocommerce_downloadable_product_permissions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.731275Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_woocommerce_downloadable_product_permissions` because it could not be opened.
2025-06-10T12:22:27.731887Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.732225Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.732529Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.733047Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_woocommerce_log.ibd' OS error: 103
2025-06-10T12:22:27.733460Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.733777Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.734247Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_woocommerce_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.734981Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_woocommerce_log` because it could not be opened.
2025-06-10T12:22:27.735502Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.735755Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.736109Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.736470Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_woocommerce_order_itemmeta.ibd' OS error: 103
2025-06-10T12:22:27.736818Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.737243Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.737677Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_woocommerce_order_itemmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.738386Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_woocommerce_order_itemmeta` because it could not be opened.
2025-06-10T12:22:27.738856Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.739200Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.739601Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.740054Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_woocommerce_order_items.ibd' OS error: 103
2025-06-10T12:22:27.740403Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.740655Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.741202Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_woocommerce_order_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.741997Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_woocommerce_order_items` because it could not be opened.
2025-06-10T12:22:27.742397Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.742648Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.742972Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.743349Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_woocommerce_payment_tokenmeta.ibd' OS error: 103
2025-06-10T12:22:27.743699Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.744103Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.744510Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_woocommerce_payment_tokenmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.745207Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_woocommerce_payment_tokenmeta` because it could not be opened.
2025-06-10T12:22:27.745893Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.746188Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.746475Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.746923Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_woocommerce_payment_tokens.ibd' OS error: 103
2025-06-10T12:22:27.747357Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.747611Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.748097Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_woocommerce_payment_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.748734Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_woocommerce_payment_tokens` because it could not be opened.
2025-06-10T12:22:27.749429Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.749954Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.750436Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.750906Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_woocommerce_sessions.ibd' OS error: 103
2025-06-10T12:22:27.751339Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.751599Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.752044Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_woocommerce_sessions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.752633Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_woocommerce_sessions` because it could not be opened.
2025-06-10T12:22:27.753152Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.753445Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.753711Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.754178Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_woocommerce_shipping_zone_locations.ibd' OS error: 103
2025-06-10T12:22:27.754721Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.755059Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.755470Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_woocommerce_shipping_zone_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.756263Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_woocommerce_shipping_zone_locations` because it could not be opened.
2025-06-10T12:22:27.757087Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.757378Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.757643Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.758182Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_woocommerce_shipping_zone_methods.ibd' OS error: 103
2025-06-10T12:22:27.758573Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.758855Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.759275Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_woocommerce_shipping_zone_methods`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.759979Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_woocommerce_shipping_zone_methods` because it could not be opened.
2025-06-10T12:22:27.760482Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.760802Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.761098Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.761495Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_woocommerce_shipping_zones.ibd' OS error: 103
2025-06-10T12:22:27.762016Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.762327Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.762820Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_woocommerce_shipping_zones`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.763479Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_woocommerce_shipping_zones` because it could not be opened.
2025-06-10T12:22:27.764183Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.764479Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.764832Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.765227Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_woocommerce_tax_rate_locations.ibd' OS error: 103
2025-06-10T12:22:27.765587Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.765936Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.766328Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_woocommerce_tax_rate_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.767014Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_woocommerce_tax_rate_locations` because it could not be opened.
2025-06-10T12:22:27.767448Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.767714Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.768050Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.768437Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_woocommerce_tax_rates.ibd' OS error: 103
2025-06-10T12:22:27.768893Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.769209Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.769627Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_woocommerce_tax_rates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.770240Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_woocommerce_tax_rates` because it could not be opened.
2025-06-10T12:22:27.770640Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.770988Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.771247Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.771614Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:27.772041Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.772295Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.772688Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.773349Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:27.773808Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.774132Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.774391Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.774888Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:27.775209Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.775460Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.775958Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.776511Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:27.776971Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.777235Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.777494Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.777974Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:27.778304Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.778556Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.779097Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.779685Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:27.780750Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.781324Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.781630Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.782144Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh2\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:27.782554Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.783027Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.783501Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh2/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.784337Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh2/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:27.784810Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.785275Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.785551Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.785969Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_actionscheduler_actions.ibd' OS error: 103
2025-06-10T12:22:27.786476Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.786801Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.787217Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_actionscheduler_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.787877Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_actionscheduler_actions` because it could not be opened.
2025-06-10T12:22:27.788341Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.788621Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.788968Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.789391Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_actionscheduler_claims.ibd' OS error: 103
2025-06-10T12:22:27.789758Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.790011Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.790486Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_actionscheduler_claims`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.791144Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_actionscheduler_claims` because it could not be opened.
2025-06-10T12:22:27.791725Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.792002Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.792353Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.792751Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_actionscheduler_groups.ibd' OS error: 103
2025-06-10T12:22:27.793103Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.793521Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.794026Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_actionscheduler_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.794867Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_actionscheduler_groups` because it could not be opened.
2025-06-10T12:22:27.795422Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.795682Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.795941Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.796359Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_actionscheduler_logs.ibd' OS error: 103
2025-06-10T12:22:27.796704Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.797171Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.797728Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_actionscheduler_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.798400Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_actionscheduler_logs` because it could not be opened.
2025-06-10T12:22:27.798792Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.799044Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.799374Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.799741Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:27.800057Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.800407Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.800943Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.801608Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:27.802105Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.802464Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.802762Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.803130Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_comments.ibd' OS error: 103
2025-06-10T12:22:27.803766Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.804050Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.804556Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.805282Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_comments` because it could not be opened.
2025-06-10T12:22:27.805699Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.805957Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.806262Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.806708Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_links.ibd' OS error: 103
2025-06-10T12:22:27.807013Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.807401Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.807899Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.808640Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_links` because it could not be opened.
2025-06-10T12:22:27.809003Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.809369Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.809684Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.810161Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_notification_logs.ibd' OS error: 103
2025-06-10T12:22:27.810599Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.810855Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.811347Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_notification_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.812119Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_notification_logs` because it could not be opened.
2025-06-10T12:22:27.812796Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.813309Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.813702Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.814070Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_options.ibd' OS error: 103
2025-06-10T12:22:27.814538Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.814790Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.815227Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.816014Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_options` because it could not be opened.
2025-06-10T12:22:27.816566Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.817084Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.817390Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.817889Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_post_views.ibd' OS error: 103
2025-06-10T12:22:27.818378Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.818788Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.819210Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_post_views`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.819883Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_post_views` because it could not be opened.
2025-06-10T12:22:27.820448Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.820728Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.820985Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.821431Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:27.821772Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.822022Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.822545Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.823128Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_postmeta` because it could not be opened.
2025-06-10T12:22:27.823655Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.823987Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.824271Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.824680Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_posts.ibd' OS error: 103
2025-06-10T12:22:27.825006Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.825266Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.825792Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.826528Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_posts` because it could not be opened.
2025-06-10T12:22:27.826974Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.827242Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.827631Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.827998Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_revslider_css.ibd' OS error: 103
2025-06-10T12:22:27.828405Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.828709Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.829105Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_revslider_css`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.829753Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_revslider_css` because it could not be opened.
2025-06-10T12:22:27.830127Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.830464Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.830725Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.831090Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_revslider_css_bkp.ibd' OS error: 103
2025-06-10T12:22:27.831551Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.831802Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.832195Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_revslider_css_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.832870Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_revslider_css_bkp` because it could not be opened.
2025-06-10T12:22:27.833352Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.833639Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.833907Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.834285Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_revslider_layer_animations.ibd' OS error: 103
2025-06-10T12:22:27.834753Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.835024Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.835560Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_revslider_layer_animations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.836375Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_revslider_layer_animations` because it could not be opened.
2025-06-10T12:22:27.836913Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.837172Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.837486Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.837916Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_revslider_layer_animations_bkp.ibd' OS error: 103
2025-06-10T12:22:27.838376Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.838702Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.839164Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_revslider_layer_animations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.839859Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_revslider_layer_animations_bkp` because it could not be opened.
2025-06-10T12:22:27.840326Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.840622Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.840889Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.841295Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_revslider_navigations.ibd' OS error: 103
2025-06-10T12:22:27.841724Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.842054Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.842549Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_revslider_navigations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.843209Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_revslider_navigations` because it could not be opened.
2025-06-10T12:22:27.843754Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.844086Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.844475Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.844954Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_revslider_navigations_bkp.ibd' OS error: 103
2025-06-10T12:22:27.845455Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.845818Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.846209Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_revslider_navigations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.846867Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_revslider_navigations_bkp` because it could not be opened.
2025-06-10T12:22:27.847411Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.847682Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.848088Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.848928Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_revslider_sliders.ibd' OS error: 103
2025-06-10T12:22:27.849382Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.849782Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.850392Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_revslider_sliders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.851284Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_revslider_sliders` because it could not be opened.
2025-06-10T12:22:27.851872Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.852199Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.852480Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.852864Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_revslider_sliders_bkp.ibd' OS error: 103
2025-06-10T12:22:27.853280Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.853544Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.854006Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_revslider_sliders_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.854601Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_revslider_sliders_bkp` because it could not be opened.
2025-06-10T12:22:27.855144Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.855421Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.855702Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.856172Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_revslider_slides.ibd' OS error: 103
2025-06-10T12:22:27.856524Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.856852Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.857433Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_revslider_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.858130Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_revslider_slides` because it could not be opened.
2025-06-10T12:22:27.858598Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.858925Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.859246Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.859657Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_revslider_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:27.860130Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.860383Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.860777Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_revslider_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.861471Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_revslider_slides_bkp` because it could not be opened.
2025-06-10T12:22:27.861952Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.862241Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.862505Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.862891Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_revslider_static_slides.ibd' OS error: 103
2025-06-10T12:22:27.863576Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.863895Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.864354Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_revslider_static_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.865044Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_revslider_static_slides` because it could not be opened.
2025-06-10T12:22:27.865466Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.865724Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.866086Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.866449Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_revslider_static_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:27.866802Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.867178Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.867573Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_revslider_static_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.868337Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_revslider_static_slides_bkp` because it could not be opened.
2025-06-10T12:22:27.868990Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.869266Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.869537Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.870008Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:27.870381Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.870646Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.871255Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.871898Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:27.872315Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.872579Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.872911Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.873301Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:27.873640Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.873965Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.874434Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.875097Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:27.875525Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.875793Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.876234Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.876668Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:27.877078Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.877346Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.877764Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.878372Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_termmeta` because it could not be opened.
2025-06-10T12:22:27.878782Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.879104Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.879426Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.879916Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_terms.ibd' OS error: 103
2025-06-10T12:22:27.881540Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.882193Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.882684Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.883273Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_terms` because it could not be opened.
2025-06-10T12:22:27.883724Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.883998Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.884281Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.884856Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:27.885289Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.885637Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.886055Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.886694Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_usermeta` because it could not be opened.
2025-06-10T12:22:27.887254Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.887520Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.887907Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.888282Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_users.ibd' OS error: 103
2025-06-10T12:22:27.888698Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.889042Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.889442Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.890241Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_users` because it could not be opened.
2025-06-10T12:22:27.890806Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.891064Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.891321Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.891773Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_wc_admin_note_actions.ibd' OS error: 103
2025-06-10T12:22:27.892135Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.892385Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.892842Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_wc_admin_note_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.893433Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_wc_admin_note_actions` because it could not be opened.
2025-06-10T12:22:27.893970Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.894215Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.894484Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.894933Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_wc_admin_notes.ibd' OS error: 103
2025-06-10T12:22:27.895246Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.895488Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.895993Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_wc_admin_notes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.896576Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_wc_admin_notes` because it could not be opened.
2025-06-10T12:22:27.897074Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.897383Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.897721Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.898448Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_wc_category_lookup.ibd' OS error: 103
2025-06-10T12:22:27.898859Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.899169Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.899791Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_wc_category_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.900433Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_wc_category_lookup` because it could not be opened.
2025-06-10T12:22:27.900963Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.901237Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.901554Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.901954Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_wc_customer_lookup.ibd' OS error: 103
2025-06-10T12:22:27.902310Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.902625Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.903045Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_wc_customer_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.903701Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_wc_customer_lookup` because it could not be opened.
2025-06-10T12:22:27.904146Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.904414Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.904768Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.905161Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_wc_download_log.ibd' OS error: 103
2025-06-10T12:22:27.905546Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.905831Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.906250Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_wc_download_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.906925Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_wc_download_log` because it could not be opened.
2025-06-10T12:22:27.907338Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.907695Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.907972Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.908423Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_wc_order_coupon_lookup.ibd' OS error: 103
2025-06-10T12:22:27.908810Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.909081Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.909558Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_wc_order_coupon_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.910158Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_wc_order_coupon_lookup` because it could not be opened.
2025-06-10T12:22:27.910647Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.910943Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.911393Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.911818Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_wc_order_product_lookup.ibd' OS error: 103
2025-06-10T12:22:27.912235Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.912551Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.913001Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_wc_order_product_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.913712Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_wc_order_product_lookup` because it could not be opened.
2025-06-10T12:22:27.914385Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.914701Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.915014Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.915457Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_wc_order_stats.ibd' OS error: 103
2025-06-10T12:22:27.915811Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.916099Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.916520Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_wc_order_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.917143Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_wc_order_stats` because it could not be opened.
2025-06-10T12:22:27.917603Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.917880Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.918197Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.918612Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_wc_order_tax_lookup.ibd' OS error: 103
2025-06-10T12:22:27.919055Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.919368Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.919779Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_wc_order_tax_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.920496Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_wc_order_tax_lookup` because it could not be opened.
2025-06-10T12:22:27.921168Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.921488Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.921824Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.922251Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_wc_product_meta_lookup.ibd' OS error: 103
2025-06-10T12:22:27.922590Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.922840Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.923384Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_wc_product_meta_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.924006Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_wc_product_meta_lookup` because it could not be opened.
2025-06-10T12:22:27.924519Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.924779Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.925126Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.925504Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_wc_reserved_stock.ibd' OS error: 103
2025-06-10T12:22:27.925898Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.926235Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.926659Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_wc_reserved_stock`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.927301Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_wc_reserved_stock` because it could not be opened.
2025-06-10T12:22:27.927708Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.928033Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.928310Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.928696Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_wc_tax_rate_classes.ibd' OS error: 103
2025-06-10T12:22:27.929112Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.929378Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.929791Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_wc_tax_rate_classes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.930522Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_wc_tax_rate_classes` because it could not be opened.
2025-06-10T12:22:27.930922Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.931257Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.931519Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.931888Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_wc_webhooks.ibd' OS error: 103
2025-06-10T12:22:27.932302Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.932610Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.933125Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_wc_webhooks`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.933741Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_wc_webhooks` because it could not be opened.
2025-06-10T12:22:27.934285Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.934543Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.934802Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.935243Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_woocommerce_api_keys.ibd' OS error: 103
2025-06-10T12:22:27.935580Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.936041Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.936483Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_woocommerce_api_keys`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.937221Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_woocommerce_api_keys` because it could not be opened.
2025-06-10T12:22:27.937700Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.938018Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.938400Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.938770Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_woocommerce_attribute_taxonomies.ibd' OS error: 103
2025-06-10T12:22:27.939235Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.939490Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.939887Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_woocommerce_attribute_taxonomies`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.940635Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_woocommerce_attribute_taxonomies` because it could not be opened.
2025-06-10T12:22:27.941202Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.941470Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.941749Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.942183Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_woocommerce_downloadable_product_permissions.ibd' OS error: 103
2025-06-10T12:22:27.942590Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.942852Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.943329Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_woocommerce_downloadable_product_permissions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.944019Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_woocommerce_downloadable_product_permissions` because it could not be opened.
2025-06-10T12:22:27.944600Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.944854Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.945201Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.945570Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_woocommerce_log.ibd' OS error: 103
2025-06-10T12:22:27.945959Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.946242Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.946641Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_woocommerce_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.947307Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_woocommerce_log` because it could not be opened.
2025-06-10T12:22:27.947689Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.948028Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.948300Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.948696Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_woocommerce_order_itemmeta.ibd' OS error: 103
2025-06-10T12:22:27.949143Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.949397Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.949813Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_woocommerce_order_itemmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.950540Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_woocommerce_order_itemmeta` because it could not be opened.
2025-06-10T12:22:27.951019Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.951300Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.951621Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.952124Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_woocommerce_order_items.ibd' OS error: 103
2025-06-10T12:22:27.952515Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.952829Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.953305Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_woocommerce_order_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.953960Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_woocommerce_order_items` because it could not be opened.
2025-06-10T12:22:27.954427Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.954762Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.955257Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.955840Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_woocommerce_payment_tokenmeta.ibd' OS error: 103
2025-06-10T12:22:27.956265Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.956537Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.957026Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_woocommerce_payment_tokenmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.957639Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_woocommerce_payment_tokenmeta` because it could not be opened.
2025-06-10T12:22:27.958152Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.958417Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.958688Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.959112Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_woocommerce_payment_tokens.ibd' OS error: 103
2025-06-10T12:22:27.959477Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.959784Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.961402Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_woocommerce_payment_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.962158Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_woocommerce_payment_tokens` because it could not be opened.
2025-06-10T12:22:27.963390Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.963684Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.963962Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.964408Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_woocommerce_sessions.ibd' OS error: 103
2025-06-10T12:22:27.964766Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.965031Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.965588Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_woocommerce_sessions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.966559Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_woocommerce_sessions` because it could not be opened.
2025-06-10T12:22:27.967585Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.968220Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.968571Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.968978Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_woocommerce_shipping_zone_locations.ibd' OS error: 103
2025-06-10T12:22:27.969412Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.969837Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.970384Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_woocommerce_shipping_zone_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.971100Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_woocommerce_shipping_zone_locations` because it could not be opened.
2025-06-10T12:22:27.971603Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.971869Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.972137Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.972670Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_woocommerce_shipping_zone_methods.ibd' OS error: 103
2025-06-10T12:22:27.973052Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.973327Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.973738Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_woocommerce_shipping_zone_methods`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.974427Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_woocommerce_shipping_zone_methods` because it could not be opened.
2025-06-10T12:22:27.974863Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.975128Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.975445Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.975826Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_woocommerce_shipping_zones.ibd' OS error: 103
2025-06-10T12:22:27.976309Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.976602Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.977006Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_woocommerce_shipping_zones`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.977700Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_woocommerce_shipping_zones` because it could not be opened.
2025-06-10T12:22:27.978112Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.978479Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.978739Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.979111Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_woocommerce_tax_rate_locations.ibd' OS error: 103
2025-06-10T12:22:27.979636Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.979965Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.980459Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_woocommerce_tax_rate_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.981080Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_woocommerce_tax_rate_locations` because it could not be opened.
2025-06-10T12:22:27.981587Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.981853Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.982132Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.982586Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_woocommerce_tax_rates.ibd' OS error: 103
2025-06-10T12:22:27.983014Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.983309Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.983850Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_woocommerce_tax_rates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.984602Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_woocommerce_tax_rates` because it could not be opened.
2025-06-10T12:22:27.985106Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.985470Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.985748Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.986135Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:27.986553Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.986821Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.987237Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.987882Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:27.988508Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.988780Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.989053Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.989547Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:27.989892Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.990159Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.990592Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.991159Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:27.991567Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.992239Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.993257Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.993660Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:27.994078Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.994362Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.994793Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.995426Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:27.995845Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.996111Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:27.996729Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:27.997144Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_tripoh3\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:27.997548Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:27.997818Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:27.998302Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_tripoh3/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:27.999063Z 0 [Warning] InnoDB: Ignoring tablespace `client_tripoh3/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:27.999593Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:27.999872Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.000150Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.000606Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_actionscheduler_actions.ibd' OS error: 103
2025-06-10T12:22:28.001003Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.001310Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.001756Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_actionscheduler_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.002387Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_actionscheduler_actions` because it could not be opened.
2025-06-10T12:22:28.002840Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.003399Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.003691Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.004144Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_actionscheduler_claims.ibd' OS error: 103
2025-06-10T12:22:28.004559Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.004824Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.005315Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_actionscheduler_claims`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.005915Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_actionscheduler_claims` because it could not be opened.
2025-06-10T12:22:28.006426Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.006712Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.007031Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.007457Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_actionscheduler_groups.ibd' OS error: 103
2025-06-10T12:22:28.007881Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.008150Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.008591Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_actionscheduler_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.009196Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_actionscheduler_groups` because it could not be opened.
2025-06-10T12:22:28.009760Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.010037Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.010375Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.010757Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_actionscheduler_logs.ibd' OS error: 103
2025-06-10T12:22:28.011104Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.011502Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.012039Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_actionscheduler_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.012738Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_actionscheduler_logs` because it could not be opened.
2025-06-10T12:22:28.013158Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.013501Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.013830Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.014271Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_bwg_album.ibd' OS error: 103
2025-06-10T12:22:28.014625Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.014893Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.015336Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_bwg_album`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.015917Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_bwg_album` because it could not be opened.
2025-06-10T12:22:28.016357Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.016624Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.016898Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.017316Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_bwg_album_gallery.ibd' OS error: 103
2025-06-10T12:22:28.017674Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.017941Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.018505Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_bwg_album_gallery`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.019261Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_bwg_album_gallery` because it could not be opened.
2025-06-10T12:22:28.019738Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.020030Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.020411Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.020918Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_bwg_file_paths.ibd' OS error: 103
2025-06-10T12:22:28.021362Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.021658Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.022265Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_bwg_file_paths`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.022883Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_bwg_file_paths` because it could not be opened.
2025-06-10T12:22:28.023391Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.023660Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.023934Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.024389Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_bwg_gallery.ibd' OS error: 103
2025-06-10T12:22:28.024807Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.025072Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.025697Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_bwg_gallery`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.026625Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_bwg_gallery` because it could not be opened.
2025-06-10T12:22:28.027418Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.027696Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.027998Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.028478Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_bwg_image.ibd' OS error: 103
2025-06-10T12:22:28.028818Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.029086Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.029577Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_bwg_image`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.030164Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_bwg_image` because it could not be opened.
2025-06-10T12:22:28.030658Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.030932Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.031210Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.031671Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_bwg_image_comment.ibd' OS error: 103
2025-06-10T12:22:28.032033Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.032302Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.032798Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_bwg_image_comment`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.033477Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_bwg_image_comment` because it could not be opened.
2025-06-10T12:22:28.034011Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.034312Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.034679Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.035074Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_bwg_image_rate.ibd' OS error: 103
2025-06-10T12:22:28.035595Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.035884Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.036289Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_bwg_image_rate`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.036968Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_bwg_image_rate` because it could not be opened.
2025-06-10T12:22:28.037427Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.037703Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.038081Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.038667Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_bwg_image_tag.ibd' OS error: 103
2025-06-10T12:22:28.039018Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.039282Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.039878Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_bwg_image_tag`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.040656Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_bwg_image_tag` because it could not be opened.
2025-06-10T12:22:28.041077Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.041518Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.042185Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.042657Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_bwg_shortcode.ibd' OS error: 103
2025-06-10T12:22:28.043075Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.043469Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.043939Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_bwg_shortcode`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.044753Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_bwg_shortcode` because it could not be opened.
2025-06-10T12:22:28.045349Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.045631Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.045991Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.046440Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_bwg_theme.ibd' OS error: 103
2025-06-10T12:22:28.046785Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.047054Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.047584Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_bwg_theme`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.048228Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_bwg_theme` because it could not be opened.
2025-06-10T12:22:28.048703Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.048977Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.049377Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.049973Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:28.050583Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.050996Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.051697Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.052710Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:28.053353Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.053636Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.053908Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.054356Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_comments.ibd' OS error: 103
2025-06-10T12:22:28.054701Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.054961Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.055455Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.057114Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_comments` because it could not be opened.
2025-06-10T12:22:28.058549Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.058893Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.059209Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.059624Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:28.059950Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.060235Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.060729Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.061340Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_fbv` because it could not be opened.
2025-06-10T12:22:28.061822Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.062123Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.062447Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.062843Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:28.063247Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.063550Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.063967Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.064670Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:28.065151Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.065602Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.065933Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.066440Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_links.ibd' OS error: 103
2025-06-10T12:22:28.066786Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.067041Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.067522Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.068059Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_links` because it could not be opened.
2025-06-10T12:22:28.068582Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.068841Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.069097Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.069565Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_options.ibd' OS error: 103
2025-06-10T12:22:28.069880Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.070128Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.070793Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.071417Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_options` because it could not be opened.
2025-06-10T12:22:28.071964Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.072261Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.072595Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.073047Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_post_views.ibd' OS error: 103
2025-06-10T12:22:28.073442Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.073703Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.074112Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_post_views`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.074726Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_post_views` because it could not be opened.
2025-06-10T12:22:28.075124Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.075439Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.075730Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.076110Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:28.076479Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.076792Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.077228Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.077818Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_postmeta` because it could not be opened.
2025-06-10T12:22:28.078236Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.078552Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.078846Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.079276Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_posts.ibd' OS error: 103
2025-06-10T12:22:28.079629Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.079890Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.080711Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.081370Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_posts` because it could not be opened.
2025-06-10T12:22:28.081819Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.082121Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.082637Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.083130Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_redirection_404.ibd' OS error: 103
2025-06-10T12:22:28.083626Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.083953Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.084516Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_redirection_404`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.085156Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_redirection_404` because it could not be opened.
2025-06-10T12:22:28.085726Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.086051Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.086398Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.086796Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_redirection_groups.ibd' OS error: 103
2025-06-10T12:22:28.087251Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.087526Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.087939Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_redirection_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.089312Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_redirection_groups` because it could not be opened.
2025-06-10T12:22:28.090737Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.091067Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.091349Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.091792Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_redirection_items.ibd' OS error: 103
2025-06-10T12:22:28.092431Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.092786Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.093219Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_redirection_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.093920Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_redirection_items` because it could not be opened.
2025-06-10T12:22:28.094481Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.094828Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.095135Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.095668Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_redirection_logs.ibd' OS error: 103
2025-06-10T12:22:28.096100Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.096356Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.096884Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_redirection_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.097462Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_redirection_logs` because it could not be opened.
2025-06-10T12:22:28.098095Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.098393Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.098801Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.099176Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_revslider_css.ibd' OS error: 103
2025-06-10T12:22:28.099635Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.099920Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.100344Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_revslider_css`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.101002Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_revslider_css` because it could not be opened.
2025-06-10T12:22:28.101414Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.101793Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.102051Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.102419Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_revslider_css_bkp.ibd' OS error: 103
2025-06-10T12:22:28.102891Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.103140Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.103609Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_revslider_css_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.104211Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_revslider_css_bkp` because it could not be opened.
2025-06-10T12:22:28.104662Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.104929Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.105220Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.105828Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_revslider_layer_animations.ibd' OS error: 103
2025-06-10T12:22:28.106216Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.106475Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.107039Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_revslider_layer_animations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.107799Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_revslider_layer_animations` because it could not be opened.
2025-06-10T12:22:28.108254Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.108510Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.108901Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.109266Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_revslider_layer_animations_bkp.ibd' OS error: 103
2025-06-10T12:22:28.109815Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.110131Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.110559Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_revslider_layer_animations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.111179Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_revslider_layer_animations_bkp` because it could not be opened.
2025-06-10T12:22:28.111690Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.112063Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.112351Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.112785Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_revslider_navigations.ibd' OS error: 103
2025-06-10T12:22:28.113133Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.113382Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.113915Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_revslider_navigations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.114571Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_revslider_navigations` because it could not be opened.
2025-06-10T12:22:28.115232Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.115732Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.116024Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.116408Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_revslider_navigations_bkp.ibd' OS error: 103
2025-06-10T12:22:28.116853Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.117118Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.117548Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_revslider_navigations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.118144Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_revslider_navigations_bkp` because it could not be opened.
2025-06-10T12:22:28.118684Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.119085Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.119366Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.120100Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_revslider_sliders.ibd' OS error: 103
2025-06-10T12:22:28.120679Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.121264Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.121747Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_revslider_sliders`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.122458Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_revslider_sliders` because it could not be opened.
2025-06-10T12:22:28.123411Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.123761Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.124038Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.124421Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_revslider_sliders_bkp.ibd' OS error: 103
2025-06-10T12:22:28.124829Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.125091Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.125502Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_revslider_sliders_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.126168Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_revslider_sliders_bkp` because it could not be opened.
2025-06-10T12:22:28.126704Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.127017Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.127279Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.127740Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_revslider_slides.ibd' OS error: 103
2025-06-10T12:22:28.128087Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.128340Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.128848Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_revslider_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.129415Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_revslider_slides` because it could not be opened.
2025-06-10T12:22:28.130024Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.130350Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.130768Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.131181Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_revslider_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:28.131594Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.131935Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.132374Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_revslider_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.133107Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_revslider_slides_bkp` because it could not be opened.
2025-06-10T12:22:28.133666Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.133972Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.134230Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.134644Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_revslider_static_slides.ibd' OS error: 103
2025-06-10T12:22:28.135007Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.135258Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.135747Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_revslider_static_slides`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.136322Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_revslider_static_slides` because it could not be opened.
2025-06-10T12:22:28.136783Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.137044Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.137315Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.137737Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_revslider_static_slides_bkp.ibd' OS error: 103
2025-06-10T12:22:28.138118Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.138378Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.139016Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_revslider_static_slides_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.139656Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_revslider_static_slides_bkp` because it could not be opened.
2025-06-10T12:22:28.140086Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.140351Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.140650Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.141033Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_sbi_instagram_feed_locator.ibd' OS error: 103
2025-06-10T12:22:28.141404Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.141716Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.142131Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_sbi_instagram_feed_locator`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.142763Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_sbi_instagram_feed_locator` because it could not be opened.
2025-06-10T12:22:28.143184Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.143448Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.143770Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.144171Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_sbi_instagram_feeds_posts.ibd' OS error: 103
2025-06-10T12:22:28.144564Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.144828Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.145395Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_sbi_instagram_feeds_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.146276Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_sbi_instagram_feeds_posts` because it could not be opened.
2025-06-10T12:22:28.147113Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.147456Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.147875Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.148275Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_sbi_instagram_posts.ibd' OS error: 103
2025-06-10T12:22:28.148734Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.149071Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.149575Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_sbi_instagram_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.150195Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_sbi_instagram_posts` because it could not be opened.
2025-06-10T12:22:28.150729Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.151013Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.151270Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.151746Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_term_relationships.ibd' OS error: 103
2025-06-10T12:22:28.152089Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.152611Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.153612Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.154676Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_term_relationships` because it could not be opened.
2025-06-10T12:22:28.155521Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.155823Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.156160Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.156554Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_term_taxonomy.ibd' OS error: 103
2025-06-10T12:22:28.156937Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.157208Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.157634Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.158286Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_term_taxonomy` because it could not be opened.
2025-06-10T12:22:28.158718Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.159021Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.159303Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.159689Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_termmeta.ibd' OS error: 103
2025-06-10T12:22:28.160122Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.160405Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.160884Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.161544Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_termmeta` because it could not be opened.
2025-06-10T12:22:28.162118Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.162412Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.162781Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.163298Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_terms.ibd' OS error: 103
2025-06-10T12:22:28.163747Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.164134Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.164622Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.165265Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_terms` because it could not be opened.
2025-06-10T12:22:28.165680Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.166011Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.166277Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.166640Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_usermeta.ibd' OS error: 103
2025-06-10T12:22:28.167042Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.167342Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.167739Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.168622Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_usermeta` because it could not be opened.
2025-06-10T12:22:28.169164Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.169424Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.169684Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.170146Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_users.ibd' OS error: 103
2025-06-10T12:22:28.170505Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.170806Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.171314Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.171895Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_users` because it could not be opened.
2025-06-10T12:22:28.172392Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.172671Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.173018Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.173402Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_wc_admin_note_actions.ibd' OS error: 103
2025-06-10T12:22:28.173753Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.174098Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.174497Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_wc_admin_note_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.175174Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_wc_admin_note_actions` because it could not be opened.
2025-06-10T12:22:28.175575Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.175824Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.176208Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.176603Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_wc_admin_notes.ibd' OS error: 103
2025-06-10T12:22:28.177085Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.177336Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.177727Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_wc_admin_notes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.178635Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_wc_admin_notes` because it could not be opened.
2025-06-10T12:22:28.179433Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.179800Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.180331Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.180993Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_wc_category_lookup.ibd' OS error: 103
2025-06-10T12:22:28.181624Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.182074Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.182560Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_wc_category_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.183198Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_wc_category_lookup` because it could not be opened.
2025-06-10T12:22:28.183632Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.183931Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.184206Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.184596Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_wc_customer_lookup.ibd' OS error: 103
2025-06-10T12:22:28.185029Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.185314Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.185753Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_wc_customer_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.186384Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_wc_customer_lookup` because it could not be opened.
2025-06-10T12:22:28.186821Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.187141Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.187415Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.187808Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_wc_download_log.ibd' OS error: 103
2025-06-10T12:22:28.188180Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.188447Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.188905Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_wc_download_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.189503Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_wc_download_log` because it could not be opened.
2025-06-10T12:22:28.189955Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.190219Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.190493Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.190919Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_wc_order_coupon_lookup.ibd' OS error: 103
2025-06-10T12:22:28.191289Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.191553Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.192001Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_wc_order_coupon_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.192611Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_wc_order_coupon_lookup` because it could not be opened.
2025-06-10T12:22:28.193064Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.193331Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.193607Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.194034Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_wc_order_product_lookup.ibd' OS error: 103
2025-06-10T12:22:28.194413Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.194677Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.195160Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_wc_order_product_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.195783Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_wc_order_product_lookup` because it could not be opened.
2025-06-10T12:22:28.196264Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.196536Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.196877Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.197269Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_wc_order_stats.ibd' OS error: 103
2025-06-10T12:22:28.197623Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.197928Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.198341Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_wc_order_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.198963Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_wc_order_stats` because it could not be opened.
2025-06-10T12:22:28.199435Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.199794Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.200066Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.200671Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_wc_order_tax_lookup.ibd' OS error: 103
2025-06-10T12:22:28.201068Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.201382Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.202021Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_wc_order_tax_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.203045Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_wc_order_tax_lookup` because it could not be opened.
2025-06-10T12:22:28.204148Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.204645Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.204965Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.205555Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_wc_product_meta_lookup.ibd' OS error: 103
2025-06-10T12:22:28.205992Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.206248Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.206689Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_wc_product_meta_lookup`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.207325Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_wc_product_meta_lookup` because it could not be opened.
2025-06-10T12:22:28.207871Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.208141Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.208407Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.208853Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_wc_reserved_stock.ibd' OS error: 103
2025-06-10T12:22:28.209205Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.209732Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.210312Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_wc_reserved_stock`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.211065Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_wc_reserved_stock` because it could not be opened.
2025-06-10T12:22:28.211592Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.211990Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.212267Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.212706Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_wc_tax_rate_classes.ibd' OS error: 103
2025-06-10T12:22:28.213096Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.213359Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.213862Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_wc_tax_rate_classes`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.214518Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_wc_tax_rate_classes` because it could not be opened.
2025-06-10T12:22:28.215088Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.215348Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.215634Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.216069Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_wc_webhooks.ibd' OS error: 103
2025-06-10T12:22:28.216392Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.216683Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.217243Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_wc_webhooks`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.218042Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_wc_webhooks` because it could not be opened.
2025-06-10T12:22:28.218482Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.218868Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.219252Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.219893Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_woocommerce_api_keys.ibd' OS error: 103
2025-06-10T12:22:28.220344Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.220657Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.221178Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_woocommerce_api_keys`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.221936Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_woocommerce_api_keys` because it could not be opened.
2025-06-10T12:22:28.222370Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.222672Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.222950Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.223318Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_woocommerce_attribute_taxonomies.ibd' OS error: 103
2025-06-10T12:22:28.223740Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.223992Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.224447Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_woocommerce_attribute_taxonomies`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.225126Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_woocommerce_attribute_taxonomies` because it could not be opened.
2025-06-10T12:22:28.225575Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.225938Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.226204Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.226572Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_woocommerce_downloadable_product_permissions.ibd' OS error: 103
2025-06-10T12:22:28.227039Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.227292Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.227804Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_woocommerce_downloadable_product_permissions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.228462Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_woocommerce_downloadable_product_permissions` because it could not be opened.
2025-06-10T12:22:28.229198Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.229482Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.229796Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.230171Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_woocommerce_log.ibd' OS error: 103
2025-06-10T12:22:28.230509Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.230825Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.231260Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_woocommerce_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.231892Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_woocommerce_log` because it could not be opened.
2025-06-10T12:22:28.232518Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.232851Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.233115Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.234372Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_woocommerce_order_itemmeta.ibd' OS error: 103
2025-06-10T12:22:28.234810Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.235161Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.235592Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_woocommerce_order_itemmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.236326Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_woocommerce_order_itemmeta` because it could not be opened.
2025-06-10T12:22:28.236876Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.237193Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.237457Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.237879Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_woocommerce_order_items.ibd' OS error: 103
2025-06-10T12:22:28.238251Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.238502Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.239012Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_woocommerce_order_items`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.239995Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_woocommerce_order_items` because it could not be opened.
2025-06-10T12:22:28.240693Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.241214Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.241556Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.242303Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_woocommerce_payment_tokenmeta.ibd' OS error: 103
2025-06-10T12:22:28.242875Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.243225Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.243876Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_woocommerce_payment_tokenmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.244573Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_woocommerce_payment_tokenmeta` because it could not be opened.
2025-06-10T12:22:28.245246Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.245555Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.245889Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.246370Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_woocommerce_payment_tokens.ibd' OS error: 103
2025-06-10T12:22:28.246754Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.247165Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.247783Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_woocommerce_payment_tokens`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.248557Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_woocommerce_payment_tokens` because it could not be opened.
2025-06-10T12:22:28.249186Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.249537Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.249940Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.250372Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_woocommerce_sessions.ibd' OS error: 103
2025-06-10T12:22:28.281355Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.281653Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.282221Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_woocommerce_sessions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.283287Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_woocommerce_sessions` because it could not be opened.
2025-06-10T12:22:28.284414Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.284925Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.285496Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.286231Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_woocommerce_shipping_zone_locations.ibd' OS error: 103
2025-06-10T12:22:28.286816Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.287105Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.287638Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_woocommerce_shipping_zone_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.288324Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_woocommerce_shipping_zone_locations` because it could not be opened.
2025-06-10T12:22:28.288921Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.289211Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.289875Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.290517Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_woocommerce_shipping_zone_methods.ibd' OS error: 103
2025-06-10T12:22:28.291086Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.291618Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.292255Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_woocommerce_shipping_zone_methods`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.293311Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_woocommerce_shipping_zone_methods` because it could not be opened.
2025-06-10T12:22:28.294405Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.294964Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.295748Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.296295Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_woocommerce_shipping_zones.ibd' OS error: 103
2025-06-10T12:22:28.297132Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.297578Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.298985Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_woocommerce_shipping_zones`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.300709Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_woocommerce_shipping_zones` because it could not be opened.
2025-06-10T12:22:28.301513Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.301994Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.302433Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.303168Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_woocommerce_tax_rate_locations.ibd' OS error: 103
2025-06-10T12:22:28.303829Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.304234Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.304927Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_woocommerce_tax_rate_locations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.305589Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_woocommerce_tax_rate_locations` because it could not be opened.
2025-06-10T12:22:28.306165Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.306431Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.307022Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.307445Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_woocommerce_tax_rates.ibd' OS error: 103
2025-06-10T12:22:28.307902Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.308257Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.308736Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_woocommerce_tax_rates`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.309464Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_woocommerce_tax_rates` because it could not be opened.
2025-06-10T12:22:28.310159Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.310756Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.311239Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.311909Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_wt_iew_action_history.ibd' OS error: 103
2025-06-10T12:22:28.312744Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.313168Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.313901Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_wt_iew_action_history`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.315056Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_wt_iew_action_history` because it could not be opened.
2025-06-10T12:22:28.315950Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.316422Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.317113Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.318051Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_wt_iew_cron.ibd' OS error: 103
2025-06-10T12:22:28.318511Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.318809Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.319831Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_wt_iew_cron`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.320878Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_wt_iew_cron` because it could not be opened.
2025-06-10T12:22:28.321393Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.321876Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.322439Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.323115Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_wt_iew_ftp.ibd' OS error: 103
2025-06-10T12:22:28.323576Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.323954Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.324442Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_wt_iew_ftp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.325345Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_wt_iew_ftp` because it could not be opened.
2025-06-10T12:22:28.325971Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.326632Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.326967Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.327430Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation1\wp_wt_iew_mapping_template.ibd' OS error: 103
2025-06-10T12:22:28.327841Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.328167Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.328674Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation1/wp_wt_iew_mapping_template`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.329442Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation1/wp_wt_iew_mapping_template` because it could not be opened.
2025-06-10T12:22:28.329910Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.330231Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.330505Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.330892Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation2\wp_actionscheduler_actions.ibd' OS error: 103
2025-06-10T12:22:28.331318Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.331722Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.332171Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation2/wp_actionscheduler_actions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.332848Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation2/wp_actionscheduler_actions` because it could not be opened.
2025-06-10T12:22:28.333965Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.334300Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.334578Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.335039Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation2\wp_actionscheduler_claims.ibd' OS error: 103
2025-06-10T12:22:28.335440Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.335736Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.336210Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation2/wp_actionscheduler_claims`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.337017Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation2/wp_actionscheduler_claims` because it could not be opened.
2025-06-10T12:22:28.337758Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.338168Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.338454Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.338862Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation2\wp_actionscheduler_groups.ibd' OS error: 103
2025-06-10T12:22:28.339254Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.339519Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.339953Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation2/wp_actionscheduler_groups`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.340644Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation2/wp_actionscheduler_groups` because it could not be opened.
2025-06-10T12:22:28.341138Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.341424Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.341727Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.342157Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation2\wp_actionscheduler_logs.ibd' OS error: 103
2025-06-10T12:22:28.342532Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.342812Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.343243Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation2/wp_actionscheduler_logs`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.343956Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation2/wp_actionscheduler_logs` because it could not be opened.
2025-06-10T12:22:28.344458Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.344748Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.345084Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.345468Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation2\wp_bwg_album.ibd' OS error: 103
2025-06-10T12:22:28.346014Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.346304Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.346744Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation2/wp_bwg_album`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.347506Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation2/wp_bwg_album` because it could not be opened.
2025-06-10T12:22:28.347980Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.348269Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.348562Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.348964Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation2\wp_bwg_album_gallery.ibd' OS error: 103
2025-06-10T12:22:28.349341Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.349604Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.350044Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation2/wp_bwg_album_gallery`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.350667Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation2/wp_bwg_album_gallery` because it could not be opened.
2025-06-10T12:22:28.351153Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.351442Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.351725Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.352133Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation2\wp_bwg_file_paths.ibd' OS error: 103
2025-06-10T12:22:28.352550Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.352820Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.354199Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation2/wp_bwg_file_paths`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.355579Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation2/wp_bwg_file_paths` because it could not be opened.
2025-06-10T12:22:28.356251Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.356549Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.357132Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.357788Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation2\wp_bwg_gallery.ibd' OS error: 103
2025-06-10T12:22:28.358150Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.358486Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.358950Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation2/wp_bwg_gallery`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.359630Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation2/wp_bwg_gallery` because it could not be opened.
2025-06-10T12:22:28.360125Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.360418Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.360857Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.361348Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation2\wp_bwg_image.ibd' OS error: 103
2025-06-10T12:22:28.361698Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.361969Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.362422Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation2/wp_bwg_image`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.363011Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation2/wp_bwg_image` because it could not be opened.
2025-06-10T12:22:28.363546Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.363916Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.364260Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.364714Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation2\wp_bwg_image_comment.ibd' OS error: 103
2025-06-10T12:22:28.365079Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.365382Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.365826Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation2/wp_bwg_image_comment`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.366448Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation2/wp_bwg_image_comment` because it could not be opened.
2025-06-10T12:22:28.366917Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.367209Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.367489Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.367890Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation2\wp_bwg_image_rate.ibd' OS error: 103
2025-06-10T12:22:28.368286Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.368549Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.369076Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation2/wp_bwg_image_rate`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.369716Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation2/wp_bwg_image_rate` because it could not be opened.
2025-06-10T12:22:28.370262Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.370570Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.370864Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.371299Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation2\wp_bwg_image_tag.ibd' OS error: 103
2025-06-10T12:22:28.371702Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.372044Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.372525Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation2/wp_bwg_image_tag`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.373149Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation2/wp_bwg_image_tag` because it could not be opened.
2025-06-10T12:22:28.373676Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.374001Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.374295Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.374680Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation2\wp_bwg_shortcode.ibd' OS error: 103
2025-06-10T12:22:28.375024Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.375343Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.375919Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation2/wp_bwg_shortcode`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.376527Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation2/wp_bwg_shortcode` because it could not be opened.
2025-06-10T12:22:28.377264Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.377564Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.377986Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.378634Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation2\wp_bwg_theme.ibd' OS error: 103
2025-06-10T12:22:28.379060Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.379427Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.380047Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation2/wp_bwg_theme`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.380871Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation2/wp_bwg_theme` because it could not be opened.
2025-06-10T12:22:28.381591Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.381929Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.382364Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.382980Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation2\wp_commentmeta.ibd' OS error: 103
2025-06-10T12:22:28.383429Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.383835Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.384401Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation2/wp_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.385157Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation2/wp_commentmeta` because it could not be opened.
2025-06-10T12:22:28.386417Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.387095Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.387574Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.388206Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation2\wp_comments.ibd' OS error: 103
2025-06-10T12:22:28.388893Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.389268Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.389699Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation2/wp_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.390705Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation2/wp_comments` because it could not be opened.
2025-06-10T12:22:28.391403Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.392000Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.392366Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.392804Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation2\wp_fbv.ibd' OS error: 103
2025-06-10T12:22:28.393242Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.393565Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.394069Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation2/wp_fbv`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.394682Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation2/wp_fbv` because it could not be opened.
2025-06-10T12:22:28.395191Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.395471Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.395821Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.396305Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation2\wp_fbv_attachment_folder.ibd' OS error: 103
2025-06-10T12:22:28.396745Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.397163Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.397608Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation2/wp_fbv_attachment_folder`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.398298Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation2/wp_fbv_attachment_folder` because it could not be opened.
2025-06-10T12:22:28.398819Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.399097Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.399376Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.399801Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation2\wp_ju_queue.ibd' OS error: 103
2025-06-10T12:22:28.400165Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.400430Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.400912Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation2/wp_ju_queue`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.401488Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation2/wp_ju_queue` because it could not be opened.
2025-06-10T12:22:28.402112Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.402443Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.402881Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.403308Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation2\wp_links.ibd' OS error: 103
2025-06-10T12:22:28.403740Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.404093Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.404617Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation2/wp_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.405287Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation2/wp_links` because it could not be opened.
2025-06-10T12:22:28.405753Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.406036Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.406315Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.406748Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation2\wp_options.ibd' OS error: 103
2025-06-10T12:22:28.407091Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.407358Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.407802Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation2/wp_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.408409Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation2/wp_options` because it could not be opened.
2025-06-10T12:22:28.408903Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.409184Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.409527Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.410067Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation2\wp_post_views.ibd' OS error: 103
2025-06-10T12:22:28.410447Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.410804Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.411486Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation2/wp_post_views`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.412150Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation2/wp_post_views` because it could not be opened.
2025-06-10T12:22:28.412583Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.412921Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.413311Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.413850Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation2\wp_postmeta.ibd' OS error: 103
2025-06-10T12:22:28.414406Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.414741Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.415194Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation2/wp_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.415895Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation2/wp_postmeta` because it could not be opened.
2025-06-10T12:22:28.416341Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.416623Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.417301Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.418506Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation2\wp_posts.ibd' OS error: 103
2025-06-10T12:22:28.419639Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.420292Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.421182Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation2/wp_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.421904Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation2/wp_posts` because it could not be opened.
2025-06-10T12:22:28.422583Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.423048Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.423639Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.424240Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation2\wp_revslider_css.ibd' OS error: 103
2025-06-10T12:22:28.424607Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.424972Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.425410Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation2/wp_revslider_css`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.426043Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation2/wp_revslider_css` because it could not be opened.
2025-06-10T12:22:28.426597Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.426978Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.427286Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.427697Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation2\wp_revslider_css_bkp.ibd' OS error: 103
2025-06-10T12:22:28.428424Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.428858Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.429396Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation2/wp_revslider_css_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.430072Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation2/wp_revslider_css_bkp` because it could not be opened.
2025-06-10T12:22:28.430595Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.430890Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.432308Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.432960Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation2\wp_revslider_layer_animations.ibd' OS error: 103
2025-06-10T12:22:28.433399Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.433703Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.434469Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation2/wp_revslider_layer_animations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.435147Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation2/wp_revslider_layer_animations` because it could not be opened.
2025-06-10T12:22:28.435815Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.436104Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.436475Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.436899Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation2\wp_revslider_layer_animations_bkp.ibd' OS error: 103
2025-06-10T12:22:28.437373Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.437667Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.438097Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation2/wp_revslider_layer_animations_bkp`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.439010Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation2/wp_revslider_layer_animations_bkp` because it could not be opened.
2025-06-10T12:22:28.439586Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.439883Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-10T12:22:28.440161Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-10T12:22:28.440677Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\client_webstation2\wp_revslider_navigations.ibd' OS error: 103
2025-06-10T12:22:28.441060Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-10T12:22:28.441439Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2025-06-10T12:22:28.441883Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `client_webstation2/wp_revslider_navigations`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2025-06-10T12:22:28.442590Z 0 [Warning] InnoDB: Ignoring tablespace `client_webstation2/wp_revslider_navigations` because it could not be opened.
2025-06-10T12:22:28.443063Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-10T12:22:28.443406Z 0 [ERROR] InnoDB: The e