Tag Info

New answers tagged

2

Just start the database normally and run DBMS_DST.UPGRADE_DATABASE Then you must see the messages "An upgrade window has been successfully ended." and "Failures:0" Double check that it succeeded by running: 1: SELECT PROPERTY_NAME, SUBSTR(property_value, 1, 30) value FROM DATABASE_PROPERTIES WHERE PROPERTY_NAME LIKE 'DST_%' ORDER BY ...


2

Actually, I think this is the opposite of a bug. the 2008 document states "Source and target tables must share the same filegroup" but it looks as though they only started paying attention to their rules in 2014. This article (made for 2014 / 2016 CTE) states "The corresponding indexes, or index partitions, must also reside in the same filegroup" TechNet


1

The error/exception is because you point to a local database with --configdb. That should be a serverip:port: ##shards/replicas: mongod --shardsvr --replSet ReplName --dbpath /data/mongodb (--port 27018) --logpath /data/log/log.log ... ##configservers: mongod --configsvr --dbpath /data/cfg (--port 27019) --logpath /data/log/log.cfg ##mongos routers: mongos ...


1

PROLOGUE Someone asked the same thing of me in my organization because everyone was using MySQL 5.5. All DB servers was upgraded over the past 8 months to MySQL 5.6. Some client applications were being affected by sql_mode change as well. ROOT CAUSE I just found out why what you did does not work and the workaround is very simple. According to MySQL 5.5 ...



Top 50 recent answers are included