Help
Join the Community
-
Documentation
Find detailed info about ServiceNow products, apps, features, and releases.
-
Impact
Drive a faster ROI and amplify your expertise with ServiceNow Impact.
-
Partner
Grow your business with promotions, news, and marketing tools for partners.
-
Store
Download certified apps and integrations that complement ServiceNow.
Hi there,
Working with Instance Scan and creating your own Scan Checks? Nice! While creating your own Scan Checks of type Table Check, you might encounter a message like below.
A Business Rule is causing this. Though what does a blacklisted table or tables too large to scan actually mean? What are those tables?
Attempt to define a check for * was aborted because the table is either blacklisted or too large to scan
Blacklisted
What are the blacklisted tables, are they listed or maintained somewhere? If these tables are maintained somewhere, can't tell. I didn't find for example a table for this. While looking into the "Abort if table is in exclusion_list" Business Rule, you'll quickly hit the boundaries. ScanUtil is referenced, a Script Include which we unfortunately cannot access.
To find out which tables are blacklisted out-of-the-box, I scripted the "isTableInExclusionList" function against every table. You can apply this through:
new sn_instance_scan.ScanUtil().isTableInExclusionList(tableName)
Outcome is 78 tables which out-of-the-box are blacklisted (on a fresh Rome-release instance). The blacklisted table are:
analytics_task
antivirus_activity
attachment_scan_history
cmdb
ml_artifact_object_store
pa_cached_forecast
pa_cached_scores
pa_migration_ignored_scores
pa_scores
pa_scores_l1
pa_scores_l2
pa_snapshots
pa_snapshots_duplicates
pa_text_indexes
pa_xmr_baselines
pa_xmr_processes
pa_xmr_signal_actions
pa_xmr_signals
stage_state
sys_attachment
sys_attachment_doc
sys_attachment_doc_v2
sys_audit
sys_import_set_row
sys_json_chunk
sys_replication_queue
task
v_ais_result_improvement_rule_condition_builder_values
v_alternate_rotation
v_atf_mutually_exclusive_test
v_cluster_nodes
v_cluster_transaction
v_customer_uploads
v_cxs_search_resource
v_db_index
v_db_trigger
v_expression_cache
v_field_creator
v_field_editor
v_file_load_order
v_formatted_schedule_report
v_index_creator
v_iostats
v_logfiles
v_metadata_delete_order
v_metadata_descendant
v_metadata_parent
v_mysql_proclist
v_mysql_status
v_mysql_variables
v_on_call
v_on_call_report_cache
v_plugin
v_private_cache
v_quota_transaction
v_rotation
v_scriptable_object
v_search_genius_result
v_shared_cache
v_sql_debug
v_st_kb_category
v_st_kb_most_viewed
v_st_kb_recently_viewed
v_st_popular_item
v_st_recent_item
v_st_sc_cat_item
v_st_sc_catalog
v_st_sc_category
v_table_creator
v_table_editor
v_transaction
v_user_rotation
v_user_session
v_wf_validation_report
v_ws_creator
v_ws_editor
v_ws_field_creator
v_ws_field_editor
Too large to scan
So what does too large to scan actually mean? You will not find an answer on this on the Service Docs for example. While watching "CCL1062-K21 - Writing custom instance scan checks" though, it is mentioned that tables too large to scan are very large tables: exceeding 10 million records.
---
That's it. Just sharing a bit of the undocumented.
| If this post helped you in any way, I would appreciate it if you hit bookmark or mark it as helpful. Interested in more articles, blogs, videos, and Share projects on Instance Scan I published? - Instance Scan |
Kind regards,
Mark
2020-2021 ServiceNow Community MVP
2020-2021 ServiceNow Developer MVP
---
