解决 'PLAN_TABLE' is old version

本文介绍了解决在使用Oracle数据库进行SQL执行计划分析时遇到的'PLAN_TABLE'isoldversion问题的方法。通过删除旧的PLAN_TABLE并重新创建来确保执行计划的准确性。

解决 'PLAN_TABLE' is old version

分析sql执行计划的时候经常遇到
'PLAN_TABLE' is old version
原因,曾经使用toad的执行计划分析,所以执行了它自带的脚本生成的plan_table

解决方式:重新创建plan_table.

SQL> explain plan for select * from scott.emp;

已解释。

SQL> select * from table(dbms_xplan.display);

PLAN_TABLE_OUTPUT
------------------------------------------------------------------------

---------------------------------------------------------------
| Id | Operation | Name | Rows | Bytes | Cost (%CPU)|
---------------------------------------------------------------
| 0 | SELECT STATEMENT | | 1 | 87 | 2 (0)|
| 1 | TABLE ACCESS FULL| EMP | 1 | 87 | 2 (0)|
---------------------------------------------------------------

Note
-----
- 'PLAN_TABLE' is old version


SQL> drop table PLAN_TABLE;


表已删除。

SQL> @?/rdbms/admin/utlxplan

表已创建。

SQL> explain plan for select * from scott.emp;

已解释。

SQL> select * from table(dbms_xplan.display);

PLAN_TABLE_OUTPUT
--------------------------------------------------------------------
Plan hash value: 3956160932

------------------------------------------------------------------------
| Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time |
------------------------------------------------------------------------
| 0 | SELECT STATEMENT | | 1 | 87 | 2 (0)| 00:00:01 |
| 1 | TABLE ACCESS FULL| EMP| 1 | 87 | 2 (0)| 00:00:01 |
------------------------------------------------------------------------

已选择8行。

ok了

<![CDATA[ SELECT CREATED_BY createdBy, CREATED_DATE createdDate, UPDATED_BY updatedBy, UPDATED_DATE updatedDate, POLICY_ID policyId, INDUSTRY_NAME industryName, COMPANY_STAFF_AMOUNT companyStaffAmount, VEHICLE_LICENCE_CODE vehicleLicenceCode, BUILDING_SIZE buildingSize, BUILDING_TYPE buildingType, USAGE_ATTRIBUTE_CODE usageAttributeCode, RUN_REGION_CODE runRegionCode, JUNKETING_TYPE junketingType, PROJECT_COST projectCost, PREM_CALCULATE_MODE premCalculateMode, VEHICLE vehicle, JUNKETING_DAYS junketingDays, RATE_TABLE_NO rateTableNo, TRADE_CODE tradeCode, WORK_AREA workArea, (select cp.value_chinese_name from t_common_parameter cp where cp.collection_code='666' and cp.value_code=WORK_AREA and rownum=1) workAreaName, TOTAL_NUMBER totalNumber, INSURE_NUMBER insureNumber, INSURE_TRADE_TYPE insureTradeType, CIRCUIT_GROUP_NO circuitGroupNo, TOTAL_PREMIUM_MAN totalPremiumMan, TOTAL_PREMIUM_CHILD totalPremiumChild, MAN_COUNT manCount, CHILD_COUNT childCount, golfClub_Name golfClubName, member_No memberNo , OLD_INSURANCE_POLICY_NO oldInsurancePolicyNo, noauto_vehicle_model noautoVehicleModel, COUNTRY country, NOAUTO_SMALL_VEHICLE_MODEL noautoSmallVehicleModel, BRAND brand, RENTAL_COMPANY rentalCompany, CHINESE_NAVIGATION chineseNavigation, START_AMOUNT startAmount, IS_TRANSNATIONAL_VEHICLE isTransnationalVehicle, RUN_REGION_ODOMETER runRegionOdometer, ORDER_ID orderId, VEHICLE_END_DATE vehicleEndDate, WRITE_BACK_URL writeBackURL, BOARD_NAME boardName, INSURE_AMOUNT insureAmount, board_address boardAddress, spouse_name spouseName, ROOM_RATES roomRates, ORDER_RENTEL orderRentel, BOARD_TUIFEI_RATIO boardTuifeiRatio, BOARD_CANCLE_TYPE boardCancleType, SPORTS_RISK_TYPE sportsRiskType, (select cp.value_chinese_name from t_common_parameter cp where cp.collection_code='299' and cp.value_code=SPORTS_RISK_TYPE and rownum=1) sportsRiskTypeName, print_remark_version printRemarkVersion, PRODUCT_VERSION productVersion, ENDORSE_CODE endorseCode, BUILDING_CONSTRUCTION buildingContruction, APPLY_BUILDING_CONTENT applyBuildingContent, APPLY_BUILDING_AREA applyBuildingArea, IS_CHARGE isCharge, applied_address appliedAddress, postCode postCode, TIME_DIFFERENT_FLAG timeDifferenceFlag, REAL_WORK_AREA_NAME realWorkAreaName, inputRate inputRate, order_flag orderFlag, out_user_name outUserName, ORDER_TYPE orderType, ORDER_TRAVEL_NAME orderTravelName, ORDER_TRAVEL_ID orderTravelId, ORDER_END_DATE orderEndDate, ORDER_TRIP_DATE orderTripDate, ORDER_TRAVEL_PRODUCT orderTravelProduct, EX_ONE totalMerchantCount, EX_TWO merchantCount, HISTORY_POLICY_MARK historyPolicyMark, HISTORY_POLICY_MARK_APPLY historyPolicyMarkApply, EX_THREE numberofPassengers, apply_city_code applyCityCode, MERCHANT_BUSINESS_SOURCE merchantBusinessSource, CONTINENT continent, RENTNUM rentNum, BUSINESS_LICENSE businessLicense, MANAGE_QUALIFICA manageQualifica, RECEPTION_DAYS receptionDays, DUTY_QUOTA dutyQuota, FAITHFUL_COEFFICIENT faithfulCoefficient, POLICY_BU policyBu, NEW_POLICY newPolicy, PROJECT_CODE projectCode, EX_FOUR exFour, INDUSTRY_DETAIL industryDetail, COMPANY_AMOUNT_PERSON companyAmountPerson, ONE_DUTY_QUOTA oneDutyQuota, TOTAL_DUTY_QUOTA totalDutyQuota, POLICY_UNDERWRITE_NO policyUnderwriteNo, commission_factor commissionFactor, CONTRACT_ID contractId, OPENID openId, renew_times renewalTimes, PREM_TYPE premType, DESTINATION destination, MININUMBER_PERSON mininumberPerson, MININUMBER_DAYS mininumberDays, TOTAL_COMPENSATION totalCompensation, RENEWAL_BUSINESS_TYPE renewalBusinessType, DOMESTIC domestic, TEL_PROCESS telProcess, CUSTOMER_NATION customerNation, IS_ADD_SINGLE isAddSingle, PEASE_POLICY_NO peasePolicyNo, SPORTS_EVENT sportsEvent, SALE_PLAN_CODE salePlanCode, SALE_PLAN_NAME salePlanName, NEED_VALUEDATE needValueDate, LAST_POLICY_NO_MORE lastPolicyNoMore, INDUSTRY_DETAIL_MIN industryDetailMin, CUSTOMER_SOURCE_EXTEND customerSourceExtend, GRACE_PERIOD gracePeriod, GUARANTEEPERIOD guaranteePeriod, GUARANTEEPERIOD_PCS guaranteePeriodPCS, ACTIVITY_CODE activityCode, MEDIA_SOURCE mediaSource, NVL((SELECT '1' FROM T_POLICY_BASE E WHERE (SELECT LL.PRODUCT_CODE FROM T_LATEST_POLICY_BASE LL WHERE LL.POLICY_NO = E.LAST_POLICY_NO) !=E.PRODUCT_CODE AND E.POLICY_ID = T.POLICY_ID),'0') turnRenewalFlag, SHARESUMSALESFEE shareSumSalesFee, UM_CODE umCode, SHARESUMSALESFEE shareSumSalesFee, TOTALSHARESUMSALESFEE totalShareSumSalesFee, region region, AUTO_RENEW_TIMES autoRenewTimes, IS_AUTO_RENEW isAutoRenew, customer_source_detail customerSourceDetail, DEDUCTION_AMOUNT deductionAmount, ISSUE_CHANNEL issueChannel, CLAIMS_FLAG claimsFlag, commission_rate commissionRate, CANCEL_AGREEMENT_DATE cancelAgreementDate, party_channel channel, contract_type contractType, CANCEL_AGREEMENT_DATE cancelAgreementDate, VEHICLE_TYPE vehicleType, OWNERSHIP_ATTRIBUTE_CODE ownershipAttributeCode, VEHICLE_TONNAGES vehicleTonnages, VEHICLE_SEATS seat, Agent_failure_reason agentfailurereason, BRAND_CHN_NAME brandChnName, FIRST_REGISTER_DATE firstRegisterDate, APPROVED_CAPACITY approvedCapacity, LIMIT_LOAD limitLoad, COMMISSION_MARK commissionMark, AXX_SEQUENCE_NO axxSequenceNo, SIMPLE_ENDORSE_FLAG simpleEndorseFlag, PAYMENT_TIMES_MARK paymentTimesMark, HSBC_INSTITUTIONS_ADDERSS HSBCInstitutionsAdderss, HSBC_INSTITUTIONS_ABBR HSBCInstitutionsAbbr, HSBC_INSTITUTIONS_NAME HSBCInstitutionsName, HSBC_STAFF_ID HSBCStaffId, MERCHANT_OPEN_ID merchantOpenId, ACHIEVEMENT achievement, FISSION_SHARE_ID fissionShareId, SYSTEM_PLAT systemPlat, SCENE_FILED sceneFiled, REGISTER_ID registerId, REGISTER_MSG registerMsg, REGISTER_STATE registerState, UNDERWRITING_PATTERN underwritingPattern, PACKAGE_TYPE packageType, internet_flag internetFlag, PAYMENT_CENTRATE paymentCentrate, inform_Type informType, price_Model priceModel, REINSURANCE_FLAG reinsuranceFlag FROM T_POLICY_EXTEND T WHERE POLICY_ID=''18458746'' ]]>转成navicate可以运行的语句
10-31
数据库表结构设计 (1)local_record_config(表名) 字段 类型 是否唯一 是否能为空 说明 id INTEGER 是 否 强制主键为1,确保单记录 bEnableLocalRecording BOOLEAN 否 否 全局启用状态(默认禁用) strSavePath TEXT 否 否 存储路径(默认值避免空路径) enumStreamType INTEGER 否 否 码流类型(0=低清,1=高清) enumDelayTime INTEGER 否 否 延迟时间约束(可选5/15/30/60秒) iFileDurationMinutes INTEGER 否 否 文件时长(分钟,范围5-60) iStorageThreshold INTEGER 否 否 存储阈值(MB,范围1-99999999) bEnableFolderLimit BOOLEAN 否 否 文件夹容量限制开关(默认启用) iFolderCapacityLimit INTEGER 否 否 文件夹容量限制(GB,范围5-99999) iPlanEntryCount INTEGER 否 否 录制计划条目数(实际等于录制计划数组的长度) 计划字段组(42条计划 × 4字段) plan_0_start INTEGER 否 是 计划0开始时间(秒) plan_0_end INTEGER 否 是 计划0结束时间(秒) plan_0_weekday INTEGER 否 是 计划0周几(0=Sunday,1=Monday,…,6=Saturday) plan_0_record_type INTEGER 否 是 计划0录制方式(0=TIMED,1=DELAYED) …(省略中间字段) … … … …(索引1到41的计划字段,命名规则相同) plan_41_start INTEGER 否 是 计划41开始时间 plan_41_end INTEGER 否 是 计划41结束时间 plan_41_weekday INTEGER 否 是 计划41周几 plan_41_record_type INTEGER 否 是 计划41录制方式 iDeviceCount INTEGER 否 否 实际设备数量(0-64),用于标识有效设备字段 设备字段组(64台设备 × 3字段) device_0_id INTEGER 否 是 设备0唯一标识(当无设备时为NULL) device_0_name TEXT 否 是 设备0显示名称 device_0_selected BOOLEAN 否 是 设备0勾选状态 …(省略中间字段) … … … …(索引1到63的设备字段,命名规则相同) device_63_id INTEGER 否 是 设备63唯一标识 device_63_name TEXT 否 是 设备63显示名称 device_63_selected BOOLEAN 否 是 设备63勾选状态 仅一条记录存储全部数据(约300+字段),字段虽多但数据总量<20KB。 简化架构、保证原子更新(如配置开关和设备状态同时生效)、减少存储碎片。 在使用SQLite时,固定字段设计可以减少运行时计算,提升稳定性。 那我这些内容如何修改?
09-20
内容概要:本文介绍了一种基于蒙特卡洛模拟和拉格朗日优化方法的电动汽车充电站有序充电调度策略,重点针对分时电价机制下的分散式优化问题。通过Matlab代码实现,构建了考虑用户充电需求、电网负荷平衡及电价波动的数学模【电动汽车充电站有序充电调度的分散式优化】基于蒙特卡诺和拉格朗日的电动汽车优化调度(分时电价调度)(Matlab代码实现)型,采用拉格朗日乘子法处理约束条件,结合蒙特卡洛方法模拟大量电动汽车的随机充电行为,实现对充电功率和时间的优化分配,旨在降低用户充电成本、平抑电网峰谷差并提升充电站运营效率。该方法体现了智能优化算法在电力系统调度中的实际应用价值。; 适合人群:具备一定电力系统基础知识和Matlab编程能力的研究生、科研人员及从事新能源汽车、智能电网相关领域的工程技术人员。; 使用场景及目标:①研究电动汽车有序充电调度策略的设计与仿真;②学习蒙特卡洛模拟与拉格朗日优化在能源系统中的联合应用;③掌握基于分时电价的需求响应优化建模方法;④为微电网、充电站运营管理提供技术支持和决策参考。; 阅读建议:建议读者结合Matlab代码深入理解算法实现细节,重点关注目标函数构建、约束条件处理及优化求解过程,可尝试调整参数设置以观察不同场景下的调度效果,进一步拓展至多目标优化或多类型负荷协调调度的研究。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值